Hi, Coming back to the SLING-1603 discussion, I have progressed on the contrib/extensions/bgservlets implementation and the API as defined in the SLING-1603-engine works for me.
I also chatted with Victor Saar who says he's been using it successfully in a different context, calling the SlingServlet service programatically. At this point I would suggest merging the SLING-1603-engine branch into bundles/engine. Utility request/response classes are available in the bgservlets bundle [1], we might want to move those elsewhere (a new commons/http bundle?), but that can be later. The SlingServlet interface can be found at [2] and the other changes in the engine bundle is just the addition of the processRequest method to the SlingMainServlet [3]. So the impact on the bundle engine's public API is only the addition of the SlingServlet service. Do people agree with this engine API addition? -Bertrand [1] http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/bgservlets/src/main/java/org/apache/sling/bgservlets/ [2] http://svn.apache.org/repos/asf/sling/branches/SLING-1603-engine/src/main/java/org/apache/sling/engine/SlingServlet.java [3] http://svn.apache.org/repos/asf/sling/branches/SLING-1603-engine/src/main/java/org/apache/sling/engine/impl/SlingMainServlet.java
