Multiple levels of Session Persistence

[Edwin Kusters]

Phil,

Stupid note perhaps but you do realize that doing this method of storing
does not guarantee that all session are kept?
- The memory version won't work in a webfarm scenario (guess you don't have
that)
- Memory only session data will get lost on for instance hardware/power
failure.
- Changes to the configuration files can also stop/start your app removing
memory sessions

This can all be perfectly acceptable but wanted to mention it anyway.

Regards,
Edwin Kusters
Hot ITem Informatica

"Phil S" <phil.scovis@hansen.NOSPAM.com> wrote in message
news:OQGdOCiSDHA.2228@tk2msftngp13.phx.gbl...

> I think that's what I'm going to end up doing, assuming there's no
> configuration setting that will do it for me.
>
> "Victor Garcia Aprea [MVP]" <vga@NOobiesSPAM.com> wrote in message
> news:#yLoj0ASDHA.3796@tk2msftngp13.phx.gbl...

> > Hi Phil,
> >
> > I've written a "PersistentStorage" type for one of my clients. It works
> > exactly like session but persist the data to a provided storage. It has

a

> > data provider model so you could add different storage targets where to
> > persist the data. Currently I've only written a MSSQL provider but its
> > working great. Basically its a type implementing IHttpModule that based

on

> > the current user id retrieves his/her previous session-data when a

request

> > comes in and saves the session-data (only if it was modified) when a

> request

> > ends.
> >
> > --
> > Victor Garcia Aprea
> > Microsoft MVP | ASP.NET
> > Looking for insights on ASP.NET? Read my blog:
> > [url]http://obies.com/vga/blog.aspx[/url]
> > To contact me remove 'NOSPAM'. Please post all questions to the

newsgroup

> > and not by private mail.
> >
> > "Phil S" <phil.scovis.NoHormelMeatProducts@hansen.com> wrote in message
> > news:%23WnHqk%23RDHA.1896@TK2MSFTNGP12.phx.gbl...

> > > I know it's possible to set the config file to keep sessions either in
> > > process or persist them.
> > >
> > > How would one go about implementing multiple layers of Session

> > availability;

> > > e.g.: Keep sessions in memory for X minutes, then maintain them out of
> > > process for Y days, then abandon them.
> > >
> > > The ultimate goal here is that sessions never expire, but active

> sessions

> > > are kept on the stove, and old zombie sessions are put in the freezer.

> > The

> > > configuration file seems to allow for the stove or the freezer, but

not

> > > both.
> > >
> > > Any help is appreciated.
> > >
> > >

> >
> >

>
>

[Phil S]

Thanks for the heads up..
Actually, I had thought of this, but for the present, we are merely
concerned with not having people time out in normal usage, such as taking a
potty break in the middle of using the site. We'll probably end up with
some kind of session server to handle short-term state management.


"Edwin Kusters" <NOSPAMeksnews@xs4all.nl> wrote in message
news:uM##kplSDHA.212@TK2MSFTNGP10.phx.gbl...

> Phil,
>
> Stupid note perhaps but you do realize that doing this method of storing
> does not guarantee that all session are kept?
> - The memory version won't work in a webfarm scenario (guess you don't

have

> that)
> - Memory only session data will get lost on for instance hardware/power
> failure.
> - Changes to the configuration files can also stop/start your app removing
> memory sessions
>
> This can all be perfectly acceptable but wanted to mention it anyway.
>
> Regards,
> Edwin Kusters
> Hot ITem Informatica
>
> "Phil S" <phil.scovis@hansen.NOSPAM.com> wrote in message
> news:OQGdOCiSDHA.2228@tk2msftngp13.phx.gbl...

> > I think that's what I'm going to end up doing, assuming there's no
> > configuration setting that will do it for me.
> >
> > "Victor Garcia Aprea [MVP]" <vga@NOobiesSPAM.com> wrote in message
> > news:#yLoj0ASDHA.3796@tk2msftngp13.phx.gbl...

> > > Hi Phil,
> > >
> > > I've written a "PersistentStorage" type for one of my clients. It

works

> > > exactly like session but persist the data to a provided storage. It

has

> a

> > > data provider model so you could add different storage targets where

to

> > > persist the data. Currently I've only written a MSSQL provider but its
> > > working great. Basically its a type implementing IHttpModule that

based

> on

> > > the current user id retrieves his/her previous session-data when a

> request

> > > comes in and saves the session-data (only if it was modified) when a

> > request

> > > ends.
> > >
> > > --
> > > Victor Garcia Aprea
> > > Microsoft MVP | ASP.NET
> > > Looking for insights on ASP.NET? Read my blog:
> > > [url]http://obies.com/vga/blog.aspx[/url]
> > > To contact me remove 'NOSPAM'. Please post all questions to the

> newsgroup

> > > and not by private mail.
> > >
> > > "Phil S" <phil.scovis.NoHormelMeatProducts@hansen.com> wrote in

message

> > > news:%23WnHqk%23RDHA.1896@TK2MSFTNGP12.phx.gbl...
> > > > I know it's possible to set the config file to keep sessions either

in

> > > > process or persist them.
> > > >
> > > > How would one go about implementing multiple layers of Session
> > > availability;
> > > > e.g.: Keep sessions in memory for X minutes, then maintain them out

of

> > > > process for Y days, then abandon them.
> > > >
> > > > The ultimate goal here is that sessions never expire, but active

> > sessions

> > > > are kept on the stove, and old zombie sessions are put in the

freezer.

> > > The
> > > > configuration file seems to allow for the stove or the freezer, but

> not

> > > > both.
> > > >
> > > > Any help is appreciated.
> > > >
> > > >
> > >
> > >

> >
> >

>
>

[John Saunders]

Why not just make the session timeout longer?

--
John Saunders
Internet Engineer
[email]john.saunders@surfcontrol.com[/email]


"Phil S" <phil.scovis@hansen.NOSPAM.com> wrote in message
news:u32evEmSDHA.1072@TK2MSFTNGP10.phx.gbl...

> Thanks for the heads up..
> Actually, I had thought of this, but for the present, we are merely
> concerned with not having people time out in normal usage, such as taking

a

> potty break in the middle of using the site. We'll probably end up with
> some kind of session server to handle short-term state management.
>
>
> "Edwin Kusters" <NOSPAMeksnews@xs4all.nl> wrote in message
> news:uM##kplSDHA.212@TK2MSFTNGP10.phx.gbl...

> > Phil,
> >
> > Stupid note perhaps but you do realize that doing this method of storing
> > does not guarantee that all session are kept?
> > - The memory version won't work in a webfarm scenario (guess you don't

> have

> > that)
> > - Memory only session data will get lost on for instance hardware/power
> > failure.
> > - Changes to the configuration files can also stop/start your app

removing

> > memory sessions
> >
> > This can all be perfectly acceptable but wanted to mention it anyway.
> >
> > Regards,
> > Edwin Kusters
> > Hot ITem Informatica
> >
> > "Phil S" <phil.scovis@hansen.NOSPAM.com> wrote in message
> > news:OQGdOCiSDHA.2228@tk2msftngp13.phx.gbl...

> > > I think that's what I'm going to end up doing, assuming there's no
> > > configuration setting that will do it for me.
> > >
> > > "Victor Garcia Aprea [MVP]" <vga@NOobiesSPAM.com> wrote in message
> > > news:#yLoj0ASDHA.3796@tk2msftngp13.phx.gbl...
> > > > Hi Phil,
> > > >
> > > > I've written a "PersistentStorage" type for one of my clients. It

> works

> > > > exactly like session but persist the data to a provided storage. It

> has

> > a

> > > > data provider model so you could add different storage targets where

> to

> > > > persist the data. Currently I've only written a MSSQL provider but

its

> > > > working great. Basically its a type implementing IHttpModule that

> based

> > on

> > > > the current user id retrieves his/her previous session-data when a

> > request

> > > > comes in and saves the session-data (only if it was modified) when a
> > > request
> > > > ends.
> > > >
> > > > --
> > > > Victor Garcia Aprea
> > > > Microsoft MVP | ASP.NET
> > > > Looking for insights on ASP.NET? Read my blog:
> > > > [url]http://obies.com/vga/blog.aspx[/url]
> > > > To contact me remove 'NOSPAM'. Please post all questions to the

> > newsgroup

> > > > and not by private mail.
> > > >
> > > > "Phil S" <phil.scovis.NoHormelMeatProducts@hansen.com> wrote in

> message

> > > > news:%23WnHqk%23RDHA.1896@TK2MSFTNGP12.phx.gbl...
> > > > > I know it's possible to set the config file to keep sessions

either

> in

> > > > > process or persist them.
> > > > >
> > > > > How would one go about implementing multiple layers of Session
> > > > availability;
> > > > > e.g.: Keep sessions in memory for X minutes, then maintain them

out

> of

> > > > > process for Y days, then abandon them.
> > > > >
> > > > > The ultimate goal here is that sessions never expire, but active
> > > sessions
> > > > > are kept on the stove, and old zombie sessions are put in the

> freezer.

> > > > The
> > > > > configuration file seems to allow for the stove or the freezer,

but

> > not

> > > > > both.
> > > > >
> > > > > Any help is appreciated.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >

> >
> >

>
>