Win a copy of Succeeding with AI this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Junilu Lacar
  • Tim Cooke
  • Jeanne Boyarsky
  • Knute Snortum
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger
  • Frits Walraven

Integrating RESTful Rails

Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Dav[id|e],

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?

Doug Hall
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
You'll never get away with this you overconfident blob! The most you will ever get is this tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic