Add interoperability with alternate session mechanisms [#1190624]

The current implementation is tightly linked with the default DB-based session handling. It would be good if the module could define an API it expects to allow it to work with alternate implementations like MongoDB sessions, where there is a feature request about this #1190620: Include something like session_limit.

Comments

Comment #1

crea commented 16 June 2011 at 17:42

Subscribing

Comment #2

johnennew commented 6 June 2013 at 20:11

This has been around for about 2 years now with little direct support.

I can see how this could be achieved from the session_limit end. Practically this would be the same as the way the Drupal mail handler works;

1. an interface defining get/count/disconnect session functions.
2. An implementing class for SQL style functions
3. A variable which defines the class that should be instantiated at run time, the default value would be the SQL class
4. Other session handlers could then define their own concrete implementation of the interface and tell Drupal to use it by setting the variable specified in 3.

I'd be happy to look at the session_limit implementation of this in a new branch but would want some help with testing, ideally with someone else producing the mongo_session implementation at the same time to prove the API.

If you're interested, let me know!