> The "DB_File" session store does not work for me. It seems to be a locking
> or flushing issue: the modified session data are not written to the
DB_File
> immediately, so that the cookie id sent to the server with the next
request
> is not found in the store and a new cookie id is generated and sent. This
of
> course breaks maintaining the state of the session. But with the next
> request maybe it works. When I shut down Apache, all missing cookies are
> written to the db file... This behaviour is not dependent on the type of
> locker used.
>
> After switching to the plain "File" store, everything just works as
> expected - great. So for me the problem is solved, although I needed some
> time to find out what is wrong (as explained it worked sometimes). Still I
> am interested in comments or solutions - maybe I did something wrong.
Please
> cc to me.
>
I guess this is the same problem as with Postgress and sessions. Because
EMbperl doesn't destroy teh session object, the data doesn't get written out
correctly (also Embperl calls the store method of Apache::Session). Maybe it
would be possible to make a similar hack as for Postgress.
I look at this after my holiday (after july, 8.)
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]
