Re: [cgiapp] CAP::Apache and CAP::Session

[Cees Hek <suppressed>]

Hi Jesse,

Good to hear from you again.  We've missed your input here in the last
little while.

On Tue, 16 Nov 2004 06:56:27 -0500, Jesse Erlbaum <suppressed> wrote:
> Before you go and modify your module, shouldn't the responsibility for
> providing a working cookie() method be on CAP::Apache?

The part I was planning to alter was the creation of a new cookie. 
This only currently uses $self->query since it is convenient, but it
could easily use CGI::Cookie directly without breaking encapsulation. 
All that really needs to be done is for this to send a valid formated
cookie string to the header_add method, so it doesn't really matter
how the string is built.

The section that looks for the current session ID in the cookies
and/or GET/POST params will still have to use the $self->query->cookie
and $self->query->param methods, since as you mention that would be
the expected behaviour.

> Michael:  If you want to use something besides CGI.pm, why don't you
> make a wrapper class which is compatible with the former?

I agree that this would probably be the ideal approach.

Cheers,

-- 
Cees Hek

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed