In this case, if it matters, we need sessions for user settings, logging,Well, if you used HTTP authentication, you'd have a nice $ENV{REMOTE_USER} once the user is authenticated.
preferences, authentication etc.
You can use it for your user settings, preferences, and apache does the authentication for you.
But of course it's no good for logging non authenticated users if you're unhappy with 'standard' apache logs. Which is why I was asking the question. Apart from super precise logging, you might not actually _need_ sessions at all.
To perhaps clarify, I was not asking for advice as to whether or not to useHubris my friend, hubris... More seriously, I don't use sessions that much. But that's because it's often possible to avoid them... using a RESTful model for your web app often helps. But then I don't know if it could be suitable for the kind of app you're writing and you don't seem much interested in this alternative so I'll stop here :-)
some sort of session management, but rather for people comments and
experience between these two (very similar looking) modules. There must be
differences, else why would people go to the effort of maintaining them ?
:-)
Best Regards, Jean-Michel.
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
