David Kaufman wrote:
i'm not sure if or how the C::A::Session Cees has announced relates to
the CGI::Session which i've used, the other Session modules that i've
seen, or others that i've heard mentioned, but the fact that there is
more than one "on the market" is a strong argument IMO for adding
another set of "has-a stubs" to CGI::App that provide consistent wrapper
interface methods around sessions (in the abstract), and defaults to
*using* one external "session-engine" module that "we all like", while
*also* providing the freedom we enjoy WRT CGI.pm, that is, the
flexibility to painlessly swap in a *different* session "engine" module
when/if the default one doesn't meet some specific need.
Hi David,
I like most of what you have said, but I don't have time right now to
answer in detail. I do however want to clarify that the
CGI::Application::Session module actually uses CGI::Session.
It just gives you a $self->session method in the spirit of $self->query
and $self->load_tmpl by returning a CGI::Session object when it is called.
Cheers,
Cees
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
