> I thought that Apache::Session releases that for me. Typically I have
> a global variable which stores the session and the globals are
> destroyed by Embperl I think which should force the sync of the
> Session object.
>
Yes
> The only problem I had to solve where the session was never released
> (only with IE5!) was in the situation of a redirect. There I needed to
> force the sync:
>
>
> [# my page.html (just a sketch) #]
>
> [-
> $session = CS::Session->getSession;
>
> $session->{'x'} = 1;
>
> $session->make_synced;
>
> $r = Apache->request;
>
> $r->header_out("Location" => "/somewhere.html");
>
> $r->status(REDIRECT);
>
> Apache::exit();
> -]
>
>
> Could it be that the session is still not released in this case and
> this would influence all subsequent accesses for this session?
>
If the session object is DESTROYED than the lock is released, but if the not
the lock will persist. The make_synced only marks the session object as sync
but will not do anythingelse.
You need to make sure that no references to the session object exists after
the end of the request. (globals inside your Embperl page will be cleaned by
Embperl, but your are responsible for all other globals)
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
