Hello, I have some questions;
1. Is the recommended way of switching between different types of handlers if you want extensionless urls to use an HttpHandlerFactory?
2. I'm using (1), and when I fail to handle the request in the CMS I want it to cascade down to the static file handler which has a number of improvements over anything I can build in managed code (response-time, security-integration, directory-listing reading settings, dynamic compression among other things).
How do I do this? In IIS6 I:
return new DefaultHttpHandler();
but that doesn't work for IIS7 and I'm not even sure that's the same way I should do it in order to reap the benefits of the built-in static file handler. (In fact I don't think it is)
My routing module knows whether my CMS can handle it or not; it that doesn't need to go into the httphandlerfactory.
3. From the above discussion it's apparent that the httphandlerfactory in fact gobbles up the request for all handlers below, or otherwise I have no idea about how to make it not do that and pass the request down. If you know how, I would like to know.
4. How important is it to implement pooling of IHttpHandlers, in terms of performance?
5. Is there a way of providing your own cache, i.e. go around the built-in cache (for very specific reasons), without having threads killed by the runtime?