> >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 new (and undocumented so
far) in 1.3.4. %udat still behaves the same and will only create one session
record per user. You need the new capibility, if you have to store the
current state of your application. For example what items are currently
viewed. If you store such things in %udat you get in trouble when the user
hits the back button or opens a new windows, because the session data will
be the same. With the new %sdat the session data will "follow" the back
button and you get different session datasets for a new window.
> This is a bit strange. Every request you add one record... I use DB_File
for
> storing. Amount af files will get higher and higher...
>
Yes, you need a way for expiring old session data. I have in mind building a
general way to do this in Apache::SessionX, but nothing is done so far.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
