On 30 Sep 2010, at 07:23, Felix Meschberger wrote: > Hi, > > On 29.09.2010 22:00, Ian Boston wrote: >> Hi, >> Is it possible to register a filter before the SlingMainServlet ? > > Short answer: No. > > Longer answer: The SlingMainServlet (or actually the > SlingRequestProcessorImpl these days) is controlling the execution of > the filters and those are only called once the SlingHttpServletRequest > and ..Response objects have been properly set up including resource and > script to be called.
Ok, (& btw, thanks for the other pointers). The reason I want to register the filter before Sling is the caching one captures certain public responses before any processing and so should be a) highly concurrent with the right cache and b) lightweight. I dont know if its my machine or the way of testing but at the moment I can only get a max of 600 request per seconds on a json properties GET, flat regardless of concurrency out of sling. If I test Tomcat 6 on a html page I get 6K/s and the throughput appears to have some relationship to the concurrency of the requests. I am going to try and trace through the code base to see if there is anything that could be making the requests single-threaded, but as a quick fix I wanted to get the caching filter right out in front. Now, its possible that some of the mods I have are causing the problem, so, here is a dumb question: Has anyone tested Sling OOTB for GET concurrency and if so, do they see single threaded behaviour or does it show linear ramp up upto the number of cores ? Ian (I am assuming that Jetty is highly concurrent, but I might need to check that in a PAX environment).
