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

["Jesse Erlbaum" <suppressed>]

Hi Cees -- 

> OK, I'll switch it to use CGI::Cookie directly instead of using it
> through CGI.pm.  I'll try and get this out soon, but patches are
> always welcome.

Before you go and modify your module, shouldn't the responsibility for
providing a working cookie() method be on CAP::Apache?

I write in the CGI-App pod, regarding using an alternative to CGI.pm:

  "...your query interface must be compatible with CGI.pm, or you must
wrap your chosen query interface in a "wrapper" class to achieve
compatibility."

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'm quite certain that the cookie() method isn't going to be the only
non-compatible feature of your approach.  I'm also quite certain that
Cees' module is not going to be the only CGI-App plug-in which assumes
(as CGI-App does) that you're using a CGI.pm compatible interface.
Rather than push the responsibility for choosing a different interface
onto other module authors, why don't you deal with it yourself?

Regarding the use of CGI::Cookie -- I think this is a violation of
encapsulation.  What if some other module author plays by the rules and
creates a CGI.pm compatible wrapper?  Cees' module won't use it, and the
wrapper won't work as a result.  It doesn't seem fair to penalize
authors who actually want to play by the rules, does it?

TTYL,

-Jesse-


--

  Jesse Erlbaum
  The Erlbaum Group
  suppressed
  Phone: 212-684-6161
  Fax: 212-684-6226



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