I'm still curious though as to the advantages to both users and or developers to implementing RESTful URI's.
I'm looking to standardize my CMS framework in every way possible, whether that means in W3C validations, meeting standard protocols or standards like RESTful URI's which no CMS I know of has excellent native support for.
Why hasn't this taken off?
Technically speaking it cleans things up a bit for me, reduces the number of lookups my routing system has to evaluate as one segment can now represent several actions (GET, POST, PUT, DELETE). So in that sense it makes sense.
I suppose for other applications, it results in a more portable system as well.
Code: Select all
user/login => Might have meant show the login form
user/login2 => Might have meant execute login request and redirectuser/login to say user/do-login at a later time down the road.
Anyone else care to chime in with experiences, benefits, side effects, caveats, etc?
So far we have:
- 1. Greater portability/stability in URI scheme
2. Cleaner/less cluttered/convoluted URI namespace
Cheers,
Alex