Hi Felix, I have a question about that:
URL for the selection of the concrete representation (script). For other > requests (POST, DELETE, ...) you want to modify the resource (and don't > care for the representation) and hence _should_ address the resource > directly without any representational detail such as selectors and > extensions." > I would like to implement two different POST features on one node. As always, a blog example :) The nodes are blog posts, one feature is posting reader comments, the second feature is trackbacks (which come along as POST requests from other blogs). For the comments I am OK with the default behavior (I do not want to overwrite POST.esp). For the trackback feature I need to implement a custom behavior (as specified or rather agreed upon by the different blog systems). How could I construct a URL that would make it possible to distinguish the two POSTs if there are no selectors? Related to this: trackback POSTs are supposed to return an xml document containing success or error messages. So in my understanding of Sling's handling of extensions for GET requests the URL for trackback POSTs should end in .xml. You might say that there is no problem, because Sling ignores the extension anyway, so it might as well be .xml, but it seems a bit inconsistent to me. I think a POST to /foo.xml should return xml and a POST to /foo.html should return html Cheers Michael -- Michael Marth | Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/
