Alexander Klimetschek wrote > On Thu, Jul 15, 2010 at 09:52, Bertrand Delacretaz > <[email protected]> wrote: >> On Wed, Jul 14, 2010 at 6:54 PM, Alexander Klimetschek <[email protected]> >> wrote: >>> On Wed, Jul 14, 2010 at 18:02, Carsten Ziegeler <[email protected]> >>> wrote: >>>> ...Why not creating plain http servlet request objects and then going >>>> through the sling main servlet? >>> >>> Interesting, how would you do that? I always thought the request >>> dispatcher is meant for this.... >> >> I'll experiment today with adding the following interface to the Sling >> API and having the SlingMainServlet implement it: >> >> /** Process an HTTP request outside of the servlet container's >> * request/response cycle */ >> public interface BackgroundRequestProcessor { >> void processRequest(HttpServletRequest req, HttpServletResponse res) { >> } >> } > > To be in line with the javax.servlet.Servlet interface that has > service() as its main method, what about calling the method > "serviceAsync()" or "serviceInBackground()"? > I think those names give a wrong impression - the request is neither processed async nor in the background - the caller of this service might run in the background; but i can also be from within a request or whatnot.
Carsten -- Carsten Ziegeler [email protected]
