A
Alex Brown
We are switching from InProc mode to StateServer mode and have a
somewhat unusual problem that I have not seen discussed.
Sometime we pass the session object to a thread by reference and the
thread will modify objects in the session. The thread does some work
and updates status in the session object. The client refreshes every
few seconds and checks the status (it is a long running task). This
works fine in InProc mode. However, this does not work in StateServer
mode. Changes to the session object in the thread are lost outside of
the scope of the thread.
I think I understand what is happening. Unually, asp serializes the
state at the end of the request after the form unload code is called.
My questions is, is there any way to force the session to serialize?
somewhat unusual problem that I have not seen discussed.
Sometime we pass the session object to a thread by reference and the
thread will modify objects in the session. The thread does some work
and updates status in the session object. The client refreshes every
few seconds and checks the status (it is a long running task). This
works fine in InProc mode. However, this does not work in StateServer
mode. Changes to the session object in the thread are lost outside of
the scope of the thread.
I think I understand what is happening. Unually, asp serializes the
state at the end of the request after the form unload code is called.
My questions is, is there any way to force the session to serialize?