471,050 Members | 1,127 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,050 software developers and data experts.

At what point to set Request / Response Filters?

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 -
Sep 3 '08 #1
0 879

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Adam | last post: by
2 posts views Thread by Rein Petersen | last post: by
reply views Thread by arunprabu | last post: by
reply views Thread by kaczmar2 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.