Hi Conor, The PUT request applied to a resource aims at creating or updating the state of this resource. But what is a resource? It is a concept (for example "the item # 2 from my list of items"), identified by a URI. Thus, you can create a resource with a PUT request, if you know "by advance" its URI. Do you see thesubtlety?
In the case you don't know its URI which happens when the "id" is generated, you must explore another ideas: - GET, OPTION, HEAD? too bad - DELETE? ahem... no. The remaining solution is the POST request applied to an "existing" resource. By convention, we use the "container" resource. Having said that, the firstResource application has been designed in a way that makes think that the "identifier" is unknown (even if the identifier is the name of the item). Best regards, Thierry Boileau > PS. Is it strange then that org.restlet.example.firstResource.ItemsResource > uses POST? > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2432336 > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2432343
