Download the PHP package upscale/swoole-session without Composer
On this page you can find all versions of the php package upscale/swoole-session. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download upscale/swoole-session
More information about upscale/swoole-session
Files in upscale/swoole-session
Package swoole-session
Short Description PHP sessions compatibility with Swoole web-server
License Apache-2.0
Homepage https://github.com/upscalesoftware/swoole-session
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 swoole-session
PHP Sessions for Swoole 
This library implements compatibility of native PHP sessions with Swoole / Open Swoole web-server.
Features:
- Transparent session start/stop
- Session ID in cookies or query string
- Native or custom session ID generator
- Automatic session data persistence
- Compliance with PHP session configuration
Installation
The library is to be installed via Composer as a dependency:
Usage
Wrap your request handling middleware into the session decorator:
Limitations
Coroutines
PHP sessions rely on the superglobal variable $_SESSION making them incompatible with the Swoole coroutines.
When a request idles for an asynchronous I/O operation, its worker process is reused to handle other request(s).
Swoole switches the call stack context, but the superglobals stay in memory shared across coroutines/requests.
Session data loaded for one request leaks to other requests causing all sorts of data integrity issues.
Disable coroutines to safely use the PHP sessions:
Output
Direct output bypassing the response instance \Swoole\Http\Response is prohibited in the Swoole environment.
Writing to the standard output stream violates the headers_sent requirement of the PHP session functions:
PHP Warning: session_start(): Cannot start session when headers already sent
Statements that "send headers" and hinder the sessions:
echo/printfwrite(STDOUT)file_put_contents('php://stdout')include 'template.phtml'header()setcookie/setrawcookie()- etc.
Output buffering commonly used by template engines avoids this pitfall, for example:
Warning! Coroutines used to "send headers" despite the output buffering until this has been fixed in Swoole 4.5.3. This is not a problem since coroutines have to be disabled for the data integrity reasons discussed above.
Blocking
Concurrent requests are prone to the session write race conditions.
The default file-based session storage of PHP employs the filesystem locking to avoid the data corruption.
Requests of the same session ID execute sequentially blocking their respective worker processes from session_start() until session_write_close().
Asynchronous coroutine-aware libraries built specifically for Swoole:
License
Licensed under the Apache License, Version 2.0.
All versions of swoole-session with dependencies
upscale/ext-swoole Version ^4.0||^5.0
upscale/ext-openswoole Version ^4.0||^22.0