On Thu, Jul 15, 2010 at 12:24, Carsten Ziegeler <[email protected]> wrote: > Alexander Klimetschek wrote >> On Thu, Jul 15, 2010 at 09:52, Bertrand Delacretaz >> <[email protected]> wrote: >>> 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.
Ok, but the interface is called "BackgroundRequestProcessor". Maybe there is a misunderstanding of the semantics of the interface. If it would be only the sling main servlet exposed as service, I'd call it simply "SlingServlet". Regards, Alex -- Alexander Klimetschek [email protected]
