This project is not covered by Drupal’s security advisory policy.
Session proxy is not a module: it is a replacement for Drupal core session handling API.
It acts as a proxy between fixed core procedural API towards a fully object oriented, more flexible and easier to extend session management API.
Basically, it strongly encapsulate the original API, separating user management against raw session storage: by using it you are able to implement any session storage engine (memcache, redis, ... ) without handling cookies and by users yourself.
Provided session engines
It ships three different session managing implementations:
- Database session handling: core default, ported to the object oriented API. It comes with an additional SQL query done more than core session.inc default implementation due to the API strong encapsulation.
- Native PHP session handling: by selecting this session management mode, you explicitely remove any core session management, and let PHP manage it. This can be useful if you intend to use low-level PHP extensions, such as Memcache or PhpRedis to handle session in PHP low-level layer instead of core. This allow to use any PHP native session storage to work gracefully: some of them are high performance.
- Cache based storage engine: Using the same session handling than core, but deporting raw session storage into a cache backend instance. You can use any already-functionning cache backend to store sessions. Sessions will use their own bin, and won't be cleared at cache clear all time.
Credits
Development
Project information
Minimally maintained
Maintainers monitor issues, but fast responses are not guaranteed.- Maintenance fixes only
Considered feature-complete by its maintainers. - Project categories: Developer tools, Performance, Integrations
28 sites report using this module- Created by pounard on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
