Re: PHP 4.0 Bug #3827: synchronizing access to sessions

On Tue, 14 Mar 2000, Andrei Zmievski wrote: > On Tue, 14 Mar 2000, Pavel Kolesnikov wrote: > > well... it was exactly the point of my "feature request" :) > > > > so it probably means that sessions work as they should work and > > i have to look for some obscure mistakes in my code :) > > I don't know if you have any mistakes in your code, but currently > sessions don't allow saving state from two separate frames. Only the > state from one frame will be saved. I'm not sure if I understand you correctly. Sascha wrote: "frame1 will lock the session file, thus blocking frame2 until frame1 has updated the session file." It means that if frame1 registeres and saves $frame1 and frame2 registeres and saves $frame2, no harm will happen. (When I wrote my feature request, I thought there's no session locking). You wrote "only the state from one frame will be saved". What do you mean by "the state"? If whole session, then you are saying something else then Sascha - or do you mean "registered variable"? If so, then everything's clear. BTW when session locking appeared in PHP? Pavel