(PHP 5 >= 5.4.0, PHP 7)

SessionHandlerInterface::openInitialise la session


abstract public bool SessionHandlerInterface::open ( string $save_path , string $session_name )

Ré-initialise une session existante ou en crée une nouvelle. Appelé lorsqu'une session est démarée ou lors de l'appel à session_start().

Liste de paramètres


Le chemin de stockage des données de session.


Le nom de la session.

Valeurs de retour

La valeur retournée (habituellement TRUE en cas de succès, FALSE si une erreur survient). Notez que cette valeur est retournée en interne à PHP pour analyse.

Voir aussi

add a note add a note

User Contributed Notes 2 notes

narf at devilix dot net
3 years ago
The suggestion that you should free the lock as soon as possible is WRONG (and for some reason, I can't downvote it right now).

Releasing the lock before the write() call is as effective as not using locks at all. The whole point is that a concurrent read() HAS to be blocked until the session is closed, otherwise you'll have race conditions.

If you care about the performance aspect, you should take care to call session_write_close() as soon as possible instead.
ross at newmail dot ru
4 years ago
You should lock your program for as shorter as possible. Lock it straight before read/write operation and unlock it just after this operation. Otherwise you will face with perfomance degradation and even lock your program at all.

You bind your session to db. Your open method opens the db connection and locks it. No other parallel requests will not be possible until the hole request to your site will be finished (and session close will be called)
To Top