Hello Sascha,
Well...
In the current case, even if it is not the cleanest solution, calling
session_end before making the redirection would solve my problem in a
acceptable manner.
The model described in this function documentation is nice, and the
existence of session_end and session_read_o
Hi Sascha,
Thanks for your answer, I now understand better why locking is not made
at a lower level. And you are right, I don't have a proposal for general
locking, I don't know php nor C nor Apache enough.
However, I really think it would be better to document this somewhere.
If it is a tech
This should not be a bug report. Please respond by email.
> ...can become code functionnality duplication. No ?
You still have to come up yet with a proposal for a general
locking facility which handles thousands of records
efficiently.
Generally, there is a best way to per
> The fact is a similar problem is happening with the mm module,
> but here I can't insert error_log to be sure... is this session
> handler "race safe" ?
Nope.
> And I'm surprised that this concurrency issue has to be solved
> on a per handler basis : isn't it functionnality duplication ?
>
