Config option to determine, if sessions should be handled by the core-implementation

Anonymous avatarAnonymous created an issue

This could be helpful to have this option. It would allow to handle session by externally (with filter, for example) and to use the methods _cpLoadSessionData and _cpSaveSessionData in this filters.

The current implementation messes with sessions allways when storage type is set, so I have to set it to "" to use the filters.

If there was an additional option, the filter could use different storage types (ram, file, cookie, db) without doubling the current code.

Reported by Kender <kender@maczewski.dyndns.org>

Comments (2)

  1. Anonymous

    Well, the default session implementation should still use the regular session options. If you want to implement some alternate implementation, you should be using some other config options ... And I made a change to the default session functions so you can use them in your alternate implementation.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.