Re: PHP 4.0 Bug #6287 Updated: serialized script execution with file sessions
| From: | Oleg Makarenko | Date: | Wed, 23 Aug 2000 08:58:00 +0000 |
| Subject: | Re: PHP 4.0 Bug #6287 Updated: serialized script execution with file sessions | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-30288@lists.php.net to get a copy of this message | ||
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... Why then mod_mm doesn't hold the lock for a whole script
life time? Nor does an mysql implementation... (there are no record locks in mysql at all)... Or
have I misread something?
>
> 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).
> After this, any SAPI module will call php_request_shutdown() which calls
> zend_deactivate_modules() which calls each request shutdown handler.)
>
But it doesn't (!) in the special case of ?=PHP_LOG. And THAT is definitely a bug.