Hi,
>
> I've noticed %mdat in Embperl 2 is not per module/page as in Embperl
> 1. Now it is per application, right?
Yes
>(Docs still claim otherwise in
> places...)
>
this should be fixed...
> I tried to play with it and it seems that Postgres as a store does
> SELECT ... FOR UPDATE,
yes
> To me it looks like only one Apache child is working and other are
> just waiting for session commit.
Mmmh, yes this seems to be the case.
I am not sure how select for update works, for the other storages the
locking works the way, that multiple pages can read at the same time, only
if one page writes it tries to get an exclusive lock. So just do write only
at the end of the page, normaly solves this locking problem.
>
> PS. When I try to empty %mdat, maybe in base.html like
> [-
> delete $mdat{$_} foreach keys %mdat;
> %mdat = ();
> -]
> it dumps empty session as expected. Now I comment out those delete
> lines and reload and %mdat has the same content as before delete.
> What's wrong?
>
Looks like Apache::Session (or the PG store) does not implement the CLEAR
method
Gerald
---------------------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
IT-Securitylösungen * Webapplikationen mit Apache/Perl/mod_perl/Embperl
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 939-122
WWW: http://www.ecos.de/ Fax: +49 6133 939-333
---------------------------------------------------------------------------
ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
---------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
