This is not an absolute truth. After all, this parent resource may be just a concept - the actual system may not have it at all.
In addition, PUT and POST may serve exactly the same purpose - create new resources. Consider the case when the object identity is expressed with a GUID. This guid may be decided upon by the client side, which could then PUT the new resource. Yet another kind of objects have integer identities and so the choice of the particular identity is made by the server - the client ought to POST the new resources of this kind. Anyway, the developer should have the freedom of choice and if it is more suitable in the particular application to group POST together with GET, PUT and DELETE then the REST framework should support it. But, leave this POST vs GET-PUT-DELETE argument. What about GET with different set of arguments? Like GET by name and GET by identity? In the native Restlet API all of the GETs are routed to the same method. The developer has then to understand what kind of GET it is. Or, again, we need to split our ServerResource. This discussion makes me think that there are really folks who think that the native Restlet API is more convenient than JAX-RS when it comes to routing the incoming requests. What am I missing here? ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2889883
