Hi Jerome, > > > > But maybe the page you return to depends on the result of the > > operation. It's not a decision the client can make. > > Ok, in this case your "/orange/editor" resource can issue a redirect to the > target URI dynamically generated.
I guess the problem is that when you design a restful application you start modeling your domain model into resources. When you need to plug in a web interface on top of this, you realize that you need a whole new set of resources (page, editor, etc). I think the post that started this thread was about what those resources should look like. I still don't have a clear answer. My client is a swing app; therefore, I'm only concerned with my domain resources. Same thing with a GWT-type UI. It'd be to have the proverbial pet shop application ported to the Restlet framework. How about running a poll to find out what presentation layer people use with their restlet app? [] dotnet/swing/swing [] flex [] html - pages assembled on the server(jsp, velocity, etc.) [] html - pages assembled on the client (one-page apps a la GWT) > > Would not that be like saying: > > /document/123;font=large > > /document/123;font=small > > > > identify 2 resources? > > Exactly, each time you change the URI, even to simply add a query parameter, > you create a different identifier. This new identifier correspond to a > different target resource! Why would you diffentiate > "/document/123;font=large" from "/document/123/large"? From the REST/HTTP > point of view, two different URIs identify two different resources. Point taken. -Vincent.
