I've been going through the code of Apache::Session trying to understand
how it works and how to use it when it occurred to me that the module
doesn't really measure up to it's name. I mean IMHO, the name is a bit
misleading.
First. It looks like the module's code is completely self-contained and
doesn't depend on anything Apache. If my observations are true, why is it
in the Apache hierarchy (except possibly for historical reasons)?
Second. It doesn't really manage sessions. It provides implementations
for different models of persistent storage (memory, FS, DB, etc.). A
complete Apache-based session managing mechanism (with session
initialization, destruction, auto-expiration, etc.) still has to be coded
on top of it.
Any comments? Shouldn't it be renamed?
Regards
Dmitry Beransky
