Config option to determine, if sessions should be handled by the core-implementation
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 <email@example.com>