You can't really mix and match RESTful and non-RESTful design can you? It would seem to spoil the whole point of REST.
Also, I saw DHH's RubyConf2006 keynote, and I'm trying my best to follow his (your) advice. So far, I'm at a mental loss for naming the "things" which form the many-to-many relationships between Users and Roles, and Roles and Rights in my RESTful authorization code. Can you help? Do you have any practical tips for when a decent name isn't readily available?
Joined: Jul 30, 2004
I think I've come up with good enough names.
Between User and Role: RoleMembership ('Membership' is likely to show up again, so the "Role" prefix gives it a bit of context.) Between Role and Right: Authority
Thanks, anyway. Feel free to comment, if you have some tips, or other examples that we might learn from.
I'm trying to think, but nothing happens. Pooh Bear
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com