Bulgaria PHP Conference 2019

SessionHandlerInterface::open

(PHP 5 >= 5.4.0, PHP 7)

SessionHandlerInterface::openセッションを開始する

説明

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

既存のセッションを再度初期化するか、あるいは新しいセッションを作成します。 セッションが開始したり session_start() が実行されたりしたときにコールされます。

パラメータ

save_path

セッションを格納/取得するパス。

session_name

セッション名。

返り値

返り値 (通常は、TRUE が成功そして FALSE が失敗を表します)。この値は PHP で内部的に処理されるものであることに注意しましょう。

参考

add a note add a note

User Contributed Notes 2 notes

up
8
narf at devilix dot net
5 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.
up
0
tony at marston-home dot demon dot co dot uk
1 year ago
Note that once $sessionName has been used to provide a value for $sessionId from the cookie data it is totally redundant as all further reading and writing of the session data is controlled by $sessionId.

If, for any reason, it becomes necessary to identify the value for $sessionName which is associated with the current $sessionId then you should use the value that was passed on the open() method. Attempting to use a value from an alternative source could have unexpected side effects.
To Top