Re: StateServer

Doing this at session end is way too late... you should save state at
every Page end.  If you have things that you want done after a session
is abandoned, you should record those actions for deferred execution
and then have a background thread that does the deed when the session
goes stale.  This can all be done without any real work using an "undo
action" table that records the stuff to be executed and a
QueueWorkItem call to insert the deferred action.

Marc

On 4/21/08, Kris Shanmugam <[email protected]> wrote:
> We've been storing some audit data / site usage data by using the
> Session_End event to persist some session data in a database. We cannot do
> this when using a StateServer (out-of-proc) as this event is not
> available. Any ideas on possible solutions when using a StateServer?
>
> Thanks,
> Kris
>
> ===================================
> This list is hosted by DevelopMentor(R)  http://www.develop.com
>
> View archives and manage your subscription(s) at http://discuss.develop.com
>


--
"Your lack of planning DOES constitute an emergency on my part... so
PLAN BETTER! "

Marc C. Brooks
http://musingmarc.blogspot.com

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com