RESTful API design - /users/:userId/resourceType vs. /resourceType/?user=:userId -


i'm spinning tires bit , i'm curious know others have decided on given same scenario.

to list of resourcetype user identified :userid restful api, uri pattern makes sense, if have resources addressed as:

/users/:userid/resourcetype // return list of resourcetype :userid

versus:

/resourcetype/?userid=:userid // query list of resourcetype

i keep thinking "do both" - feels impractical considering how many permutations possible complex resource models.

is 'pick 1 , move on' scenario or there 1 that's pragmatically better other , i'm not seeing it?

definitely don't both! you're making support work yourself. it's best if api provides 1 way thing.

either work. depends on how tightly resource types coupled users. if there's tight coupling, (1) fine. if you're not sure, or if loosely coupled, (2) preferable.


Comments

Post a Comment

Popular posts from this blog

How to logout from a login page in asp.net -

whenever click on logout button redirect me login page when im clicking on button redirect me last visited page. not using membership or windows authentication. session.abandon(); response.cache.setcacheability(httpcacheability.private); response.cache.setcacheability(httpcacheability.nocache); response.redirect("loginform.aspx"); if using session destroy session value on logout button click , can put check in app webpages if(session["sessionvaribale"].equals(null)) { response.redirect("logoutpage url"); }
Read more

Stack level too deep error after upgrade to rails 3.2 and ruby 1.9.3 -

i'm upgrading rails 3.0.9 app 3.2.13 , ruby 1.8.7 1.9.3. time try access controller action, following error started "/myapp/login" 127.0.0.1 @ 2013-07-25 07:10:06 -0600 systemstackerror (stack level deep): actionpack (3.2.13) lib/action_dispatch/middleware/reloader.rb:70 rendered /actionpack-3.2.13/lib/action_dispatch/middleware/templates/rescues/_trace.erb (1.5ms) rendered /actionpack-3.2.13/lib/action_dispatch/middleware/templates/rescues/_request_and_response.erb (5.2ms) rendered /actionpack-3.2.13/lib/action_dispatch/middleware/templates/rescues/diagnostics.erb within rescues/layout (22.6ms) the way i've been able page load without error clear out database sessions (rake db:sessions:clear) , restart rails server. allows 1 single request succeed , subsequent requests fail. i've tried comparing core config files working 3.2 app , have tried upgrade of gems. here's current gemfile: source 'http://rubygems.org' gem 'rails...
Read more