On Tue, 6 Feb 2007, Jonathan Vanasco wrote:
On Feb 6, 2007, at 4:04 AM, Issac Goldstand wrote:
Maybe I'm missing something, but why not autodetect Apache2::Request +
mod_perl2 presence and fallback to CGI if it doesn't work?
Something like:
I'm going to talk in context of CGI::Apache2::Ajax
On Tue, 6 Feb 2007, Jonathan Vanasco wrote:
I'm going to talk in context of CGI::Apache2::Ajax, as I
haven't had time to look at the rest.
Personally, I would like to see something in terms of ENV variables
that one can set to force it to use libapreq or cgi pm
Thats just because every now
On Feb 6, 2007, at 4:04 AM, Issac Goldstand wrote:
Maybe I'm missing something, but why not autodetect Apache2::Request +
mod_perl2 presence and fallback to CGI if it doesn't work?
Something like:
I'm going to talk in context of CGI::Apache2::Ajax, as I haven't had
time to look at the res
Randy Kobes wrote:
> On Tue, 6 Feb 2007, Issac Goldstand wrote:
>
>> Randy Kobes wrote:
>>> I'd be interested in any comments about these
>>> packages, including their names. CGI::Apache2::Ajax
>>> was tentatively chosen because, first of all, it only
>>> provides CGI.pm-compatible methods that
On Tue, 6 Feb 2007, Issac Goldstand wrote:
Randy Kobes wrote:
I'd be interested in any comments about these
packages, including their names. CGI::Apache2::Ajax
was tentatively chosen because, first of all, it only
provides CGI.pm-compatible methods that the above two Ajax-related
applications n
Randy Kobes wrote:
> I'd be interested in any comments about these
> packages, including their names. CGI::Apache2::Ajax
> was tentatively chosen because, first of all, it only
> provides CGI.pm-compatible methods that the above two Ajax-related
> applications need, and also, CGI::Ajax
> expects th
