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

[Michael <suppressed>]

Jesse Erlbaum wrote:

> > 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.
>
>
> I get what you're saying, but if its really that simple then Michael can
> write his own cookie() method.

The main reason I didn't do this was because the CAP::Apache wasn't a 
wrapper around Apache::Request, but a plugin for C::A. I understand 
where you could be concerned about the encapsulation of plugins and 
making sure that module authors don't have to communicate about the 
plugins. I was just trying to help people to be able to use as many 
plugins as possible with CAP::Apache. This may not be possible though.

I think it would also be breaking encapsulation if my plugin added 
methods (such as 'cookie' or 'dump') to the Apache::Request namespace. 
I'm also not convinced that a wrapper is the best solution either since 
you would then have two interfaces for the same thing to keep in mind 
while programming. Ideally I wanted to allow users to be able to 
directly use Apache::Request, not something else.

Maybe I just need to petition the libapreq people to add a cookie method 
to Apache::Request.

--
Michael Peters
Developer
Plus Three, LP


---------------------------------------------------------------------
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