PHP 8.1.0 Beta 2 available for testing

SessionHandlerInterface::open

(PHP 5 >= 5.4.0, PHP 7, PHP 8)

SessionHandlerInterface::openOturumu ilklendirir

Açıklama

abstract public SessionHandlerInterface::open(string $yol, string $isim): bool

Yeni oturumu oluşturur veya mevcut oturumu yeniden ilklendirir. Yeni oturum dahili olarak PHP tarafından ya otomatik olarak ya da session_start() kullanıldığında oluşturulur.

Değiştirgeler

yol

Oturumum saklanacağı/alınacağı yerin yolu.

isim

Oturum adı.

Dönen Değerler

Dönüş değeri (normal olarak başarılıysa true, değilse false). Bu değerin PHP tarafından dahili olarak döndürüleceği unutulmamalıdır.

Ayrıca Bakınız

add a note add a note

User Contributed Notes 2 notes

up
8
narf at devilix dot net
6 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
-1
tony at marston-home dot demon dot co dot uk
3 years 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