Re: SessionX questions

2001-08-27 Thread Gerald Richter
> >You only get a session cookie when something in %udat is modified. i.e. as > >long as you don't touch %udat no cookie is send. > Hmm, that`s strange. Imagine the user is just browsing thru pages and not > modifing any session variables. After 30 minutes of this browsing his > session will be pu

Re: SessionX questions

2001-08-27 Thread Gerald Richter
> > I noticed Embperl calls SetSessionCookie when getids[2] returns 1. > > Can you explain me the purpose of MODOFIED flag? > You only get a session cookie when something in %udat is modified. i.e. as long as you don't touch %udat no cookie is send. Gerald

Re: SessionX questions

2001-08-26 Thread Lukas Zapletal
>So OR is correct here. I see... I have another question. I noticed Embperl calls SetSessionCookie when getids[2] returns 1. Can you explain me the purpose of MODOFIED flag? What should method 'getids' return? Thanks lzap

Re: SessionX questions

2001-08-23 Thread Gerald Richter
> >Recreate_id creates a _new_ id if the given one does not exists > Can you explain the following piece of code then: > > if (!$self->{data}->{_session_id} || $self -> > {'args'}{'recreate_id'}) > > It is taken from Session.pm (what I`m learning from). > > Why you use OR (||) here? This

Re: SessionX questions

2001-08-23 Thread Lukas Zapletal
>Recreate_id creates a _new_ id if the given one does not exists Can you explain the following piece of code then: if (!$self->{data}->{_session_id} || $self -> {'args'}{'recreate_id'}) It is taken from Session.pm (what I`m learning from). Why you use OR (||) here? This should by AND (&

Re: SessionX questions

2001-08-23 Thread Gerald Richter
> >The data is let untouched. The idea is to have a unique id for every > >request, which makes it possible to keep track on session data even if the > >user hits the back button. > So the data are copied to new session record and returned? > Yes, this is only done when you use %sdat, which is ne

Re: SessionX questions

2001-08-23 Thread Lukas Zapletal
>The data is let untouched. The idea is to have a unique id for every >request, which makes it possible to keep track on session data even if the >user hits the back button. So the data are copied to new session record and returned? This is a bit strange. Every request you add one record... I use

Re: SessionX questions

2001-08-23 Thread Gerald Richter
> Hello, I`m reimplementing my old embperl session class to SessionX and I > have several questions: > > 1) I don`t see the differences between create_unknown and recreate_id. Are > they same? > Recreate_id creates a _new_ id if the given one does not exists create_unkonw cause Apache::SessionX

SessionX questions

2001-08-23 Thread Lukas Zapletal
Hello, I`m reimplementing my old embperl session class to SessionX and I have several questions: 1) I don`t see the differences between create_unknown and recreate_id. Are they same? 2) when newid is set, is data cleaned or let untouched when the new id is generated? 3) the string passed in the