SessionHandlerInterface::open

(PHP 5 >= 5.4.0, PHP 7)

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

説明

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

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

パラメータ

save_path

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

session_name

セッション名。

返り値

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

参考

add a note add a note

User Contributed Notes 2 notes

up
6
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.
up
-10
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.

Example.
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