On 03.07.2013, at 14:58, Justin Edelson <jus...@justinedelson.com> wrote:
> IMHO :operation is an aspect of the current default POST servlet. If we are > going to move more POST-specific handling into the engine, then we should > be using selectors. Yes, my main point was to have only one. You are right, selector is the broader concept, so we could drop operation here. Looking at the existing operations [0], IMO all of them could/should be replaced by a param@Something style notation. We do this with @CopyFrom already, same could be done with @Checkin etc. Even "import" can be done this way. This moves it down from some request-global operation to a parameter specific option, with the benefit of allowing multiple ones in a single request. Then the POST is always the default create-or-modify operation. With the new pipeline, things can hook in and either overlay the default behaviour for certain parameters or handle custom ones (as PostProcessors typically do). We should make it simpler to read and modify the special RequestParameter map that is passed through, it is currently quite some work to read a custom @Something and get the right path for it etc. [0] http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html#ManipulatingContent-TheSlingPostServlet%2528servlets.post%2529-SlingPostServletOperations Cheers, Alex
