Hi Toby, On Wed, Jul 30, 2008 at 1:46 PM, Tobias Bocanegra <[EMAIL PROTECTED]>wrote:
> > IMO, with the extension, you choose the type of response you want. eg, > with .json you get a json response, with .html you get a html > response. etc... > > I think selectors and extensions are a very elegant way to indicate what representation you want to get, but I think they are not necessary for POST, PUT and DELETE requests as we have a much richer way of communicating with the server here. We can send an accept header to indicate what content we expect and we can also send a Content-Type header to tell the server what type of content we are sending. This allows us to send XML and get a JSON confirmation or send URL-encoded formdata and get an HTML response. One of the main problems I see with cutting off the selectors and extensions is that the server has less knowledge about what is selector, what is extension and what is just a dot in the resource name than the client (or the application developer). So, as Felix said, the developer can easily use the base name of the resource to be specific, but the server cannot find out what the developer intended the base name to be. regards, Lars
