It does, It get the sessionlock direct inside new and not at the writeback stage. That may resolve the issue that the anonmonk has, since there is no race between the concurent requests.
| [reply] |
It does what you say, but not for MySQL. From the docs:
Note that the Transaction argument has no practical effect on the MySQL and Postgres implementations. The MySQL implementation only supports exclusive locking, and the Postgres implementation uses the transaction features of that database.
| [reply] |
But the 'exclusive locking' is what the monk want. IMHO.
And Apache::Session does that if 'Transaction => 1' even when this is no real transaction, it prevents others to write to that session until the session is untied.
Whereas without 'Transaction => 1' another request can overwrite the sessiondata with older data.
| [reply] |