Download the PHP package cache/session-handler without Composer
On this page you can find all versions of the php package cache/session-handler. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download cache/session-handler
More information about cache/session-handler
Files in cache/session-handler
Package session-handler
Short Description Locking PHP session handlers for PSR-6 and PSR-16 caches
License MIT
Homepage https://www.php-cache.com/en/latest/
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package session-handler
PSR cache session handlers
This package stores PHP sessions in a PSR-6 or PSR-16 cache. An application-supplied lock serializes access to each session.
Installation
Usage
In this example, $pool implements Psr\Cache\CacheItemPoolInterface. The application class ApplicationSessionLock implements SessionLockInterface.
The PHP Cache Bundle supplies this lock through Symfony Lock. Applications that use the session-handler package directly must provide their own implementation.
Use Psr16SessionHandler with a Psr\SimpleCache\CacheInterface instead. Both handlers use the same lock contract.
Lock contract
The lock implementation must acquire exclusive locks atomically across every process and node that can access the cache.
acquire() returns true only after it holds the session lock. A false result stops the read before cache access.
release() must release only the lock owned by the current request. Track an ownership token when the backend requires one.
Configure a lease or equivalent recovery mechanism in the backend. This prevents crashed requests from leaving permanent locks.
PSR-6 and PSR-16 do not provide atomic lock operations. Do not build a lock with a cache read followed by a cache write.
The handler acquires the lock during validateId() or read(). It keeps that lock through write() and updateTimestamp().
Every mutation verifies that it holds the lock for the same session ID. This also protects writes after session ID regeneration.
If a mutation cannot acquire its lock, it returns false without accessing the cache.
close() and destroy() release the lock. The handler also releases it when a storage operation throws an exception.
Migrating to 2.0
Version 2.0 requires a SessionLockInterface as the second constructor argument. Pass the options array as the third argument.
Contributing
Send pull requests to the main repository. Report issues on the GitHub issue tracker.
