> On Sun, Mar 23, 2008 at 7:56 PM, Ian Clarke <[EMAIL PROTECTED]> wrote: >> When is it appropriate to use a query string to pass parameters to a >> REST API call? >> >> For example, why is: >> http://blah/user/1234 >> better than: >> http://blah/user?id=1234 >> ?
On Thu, March 27, 2008 11:07, John D. Mitchell wrote: > One of the biggest reasons to use the "pure" version is that that is > fully cachable. This is to put in another strong recommendation for the recent book by Leonard Rosenthal and Sam Ruby, RESTful Web Services, which you can purchase via the "Books" link on the Restlet website: http://www.restlet.org/documentation/books This book provides deeply thought out suggestions for 'normative' practices in building RESTful services, and covers the topic of when to use "pure" resource identifiers and when to use query parameters. Aron
