Re: PHP 4.0 Bug #6287 Updated: serialized script execution with file sessions

On Wed, 23 Aug 2000, Oleg Makarenko wrote: > > Bug Database wrote: > > > ID: 6287 > > Updated by: sas > > Reported By: omakarenko@cyberplat.ru > > Status: Closed > > Bug Type: Session related > > Assigned To: > > Comments: > > > > Serialization is necessary. Otherwise, we cannot guarantee > > the integrity of session data. > > > > So that is by design... strange... That is not strange. If you would think a minute about it, it would become just obvious. > Why then mod_mm doesn't hold the lock for a whole script life > time? Because that code has not been committed yet. > Nor does an mysql implementation... (there are no record locks > in mysql at all)... Or have I misread something? There is no official MySQL implementation. > > The lock gets definitely always released. The program flow is > > not changed just because we display an image instead of > > executing the script (see php_execute_script(). It simply > > returns. > > That is how it should work. But I see completely different > behavior. The session file remains locked after the image was > send to client. It is not released as the session file remains > opened (lsof). That is not reproducable here. I don't remember a change in this area, but you might want to try a current snapshot: http://snaps.php.net/ - Sascha