Skip Menu |

This queue is for tickets about the CGI-Session CPAN distribution.

Report information
The Basics
Id: 47794
Status: new
Priority: 0/
Queue: CGI-Session

Owner: Nobody in particular
Requestors: m-uchino [...]

Bug Information
Severity: (no value)
Broken in: 4.41
Fixed in: (no value)

MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Type: text/plain
Charset: utf8
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 788
Download (untitled) / with headers
text/plain 788b
Drivers have problem about locking. For example, CGI::Session::Driver::file locks file by flock. It's OK. But, driver unlocks a file immediately after that reads a file. Now, other processes can access a file. CGI::Session just only read a file. CGI::Session will edit data and return data to a file. However, other processes may have done something. I think. The driver must continue having File-Handle after the driver locks a file. It must not unlock(close) it. While the driver object exists, the file continues being locked by keeping File-Handle. CGI::Session edit and save file safely. And, CGI::Session object is gone. Then the driver object is gone too. And the file is unlocked. It is necessary for mysql and the other drivers to continue having the lock of the record too.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to