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

[William McKee <suppressed>]

On Tue, Nov 16, 2004 at 01:30:16PM -0500, Michael wrote:
> 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 figured there was a reason for not subclassing...


> I think it would also be breaking encapsulation if my plugin added 
> methods (such as 'cookie' or 'dump') to the Apache::Request namespace. 

I would agree.


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

Which leaves me wondering where things stand between CAP::Session and
CAP::Apache. I'd like to use both but that sounds like it's not possible.


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

While you're at it, why not also petition for other common CGI
interfaces such as Dump. In porting my code to use A::R this weekend, I
was surprised that there was not better interoperability. Kinda makes
migrating more effort than it should be. Perhaps there's a good reason
for not including these methods.


William

-- 
Knowmad Services Inc.
http://www.knowmad.com

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