After reading the blog post you are referring to and reading the code of the Session
and NativeSessionStorage
classes, what I would try to mimic the behavior mentionned in the blog post is to do this:
$session = $this->get('session');
// Change the session attributes
$session->save();
session_write_close();
// Do database calls and other stuff.
I didn't test it but it should work as expected. Another solution to your problem is to use a different session storage than the NativeSessionStorage
which is used by default. You could use for example a database storage by using the PdoSessionStorage
object. This could prevent a lock from being use by PHP. See this cookbook entry for more information on how to use a database storage for sessions.
But there is no guarantee that the database system won't stack multiple requests if they are accessing the same row but it should be way faster than with the NativeSessionStorage
.
Regards,
Matt
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…