After some research I can see that when
PostRequestHandlerExecute fires,
Context.Handler is often null while in IIS6 environment it's
always the
page that just finished processing. I suspect that
Response.Redirect calls
cause this behavior in IIS7 but not in IIS6.
Since we do not want to synchronize every request, but just
requests for
the same user, Session state is used to store the Mutex.
It's my
understanding that Context.Handler is checked to ensure that
Session state
is applicable for current request. If I cannot trust
Context.Handler to be
properly set, what other way can I verify that this.Session
property can be
used. Do I have to reserve to putting try/catch blocks
around the
this.Session reference?
And finally, is this the correct way to solve this problem?
Perhaps there
are some better ways of handling this issue.
Thank you!
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
|
