Re^2: session management

Whilst you're no doubt right, from my reading and understanding, that can be frought with possible vunerabilities. I'd prefer to use a module for the low level stuff thats proven (thats why people go to the trouble of writing them).
The question is, does it matter which one? I'm leaning towards CGI::Session, but I'm not sure.

Comment on Re^2: session management

Replies are listed 'Best First'.
Re^3: session management by Joost (Canon) on Sep 04, 2008 at 09:40 UTC
CGI::Session and Apache::Session are more or less equivalent. Both work with mod_perl and CGI, so the names are a bit misleading. IIRC CGI::Session has more flexible storage back ends, so it may be easier to adjust should the default storage not work for you. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^3: session management by smiffy (Pilgrim) on Sep 04, 2008 at 09:28 UTC
I can't give you a comparison between the Apache:: and CGI:: modules because I use neither of them but bear this in mind: anything that starts with Apache:: has probably been written with mod_perl in mind, whilst anything beginning with CGI:: has probably been written as an adjunct to the CGI that comes with the Perl distribution. I had a quick look at the documentation of the Apache:: version - it says that it should work with anything (even without Apache), but my inclination would be to work with the CGI:: version if you are going to use the standard CGI module in your application. Obviously, if you are going to be working with mod_perl, you should take a look at the Apache:: version.	[reply]