At what point in the application lifecycle should a filter be applied to the Request / Response objects? Should this be done at the start of each transaction? This would make sense if a new Request / Response object is created fresh for each transaction. If these objects are reused though across transactions, then this is obviously not the approrpriate point to set these filters. I'm suspecting that my earlier issues with Response filtering (Tricky Request Filtering Issue - 9/2/2008 11:09pm) are due to the fact that I am setting this filter in place at the start of every successive transaction. Is this the correct approach, or is this incorrect? In the past, I've set the Response filter at the beginning of each request (OnAuthorizeRequest) and this has worked for me, however I'm not having similar successful results with Request filtering. Please let me know if I'm doing this incorrectly. Thanks for any guidance which you can provide. - Joseph Geretz -
