tag:blogger.com,1999:blog-6250399713867244328.post4969242346690008994..comments2008-06-07T09:16:03.701-04:00danielhttp://www.blogger.com/profile/01012067250242364513noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6250399713867244328.post-57649276330284464012008-06-07T09:16:00.000-04:002008-06-07T09:16:00.000-04:00@eric - By "ResourceMapper" you mean to suggest a different name? Yes, I see the logic, and I'd probably actually get more noticing for the purpose of replacing ActiveResource, but that's actually not the purpose of SimpleMapper.<BR/><BR/>The motive *was* originally the need to write a better (and simpler) ActiveResource, but what I really wanted to do was write a simple framework that I could later write my own formats, adapters, is easily plugin-able, uses callbacks, etc. Flexible and easy to weild to the need at hand. It's really just a structure for having persistent models, and the means to the persistence are just combinations of various connection adapters, format adapters, and plugins.<BR/><BR/>I hope it suits you well. Anyone- feel free to contact me at gems@behindlogic.com if you have any questions about implementing it.danielhttp://www.blogger.com/profile/01012067250242364513noreply@blogger.comtag:blogger.com,1999:blog-6250399713867244328.post-50526972941612079742008-06-07T07:48:00.000-04:002008-06-07T07:48:00.000-04:00ARes also just uses a URI. By default it uses id, but you can just do self.primary_key = 'email_address' if you wanted the url to looks like /users/:email_address instead of /users/:id. <BR/><BR/>But ARes has other problems, mainly in the form of bugs and crappy cross versioning compat issues. Im currently using it in a merb app and it would be nice to move to something like SimpleMapper. Maybe ResourceMapper would be a better fit? ;)Erichttp://www.blogger.com/profile/01164619698218863541noreply@blogger.com