:more comprehensive and thus less flexible.
:Apache::Session doesn't set
:cookies for you, track expiration times, or any other
:things. It just:
:-associates a unique id with a data structure
:-persistantly stores said data structure
:-recalls said data structure given the id again
If something is more comprehensive, people tend to think of it
as less flexible, and I aggree (most of the time). But this
shouldn't be the case with CGI::Session at all. It offers
the same flexibility (and even more) that Apache::Session does.
And reading and writing HTTP cookies is the feature of CGI::Session
one can make use of to condense the Perl code even more :-). You
still have to deal with such issues in CGI applications, so why
not have such utilities in the library itself ;-)
Sherzod
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.