Re: [cgiapp] Planning next CGI::App release

2004-02-09 Thread Cees Hek
[EMAIL PROTECTED] wrote: One further request, and this could generate a flame war, which I have neither the time, nor the interest to entertain, is the dedicated support of a session module, and obviously, it should also be persistantly available througout the application like query(), and

[cgiapp] Re: Planning next CGI::App release

2004-02-09 Thread Mark Stosberg
On 2004-02-09, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Gabriel: I do have one or two requests... The first is persistent access to an HTML::Template object, ala the persistant access to the CGI module via query(). I see no reason (based on my projects/experience) why it is not so.

[cgiapp] CGI::App ported to Python

2004-02-09 Thread Mark Stosberg
They say imitation is the highest form of flattery. Or something like that: CGI::App ported to python http://thraxil.org/code/cgi_app/ Time for yoga. Mark - Web Archive: http://www.mail-archive.com/[EMAIL

RE: [cgiapp] CGI::App ported to Python

2004-02-09 Thread Jesse Erlbaum
They say imitation is the highest form of flattery. Or something like that: CGI::App ported to python http://thraxil.org/code/cgi_app/ Fantastic! The cult spreads. Congrats to Anders Pearson. -Jesse- -- Jesse Erlbaum The Erlbaum Group [EMAIL PROTECTED] Phone: 212-684-6161

RE: [cgiapp] Planning next CGI::App release

2004-02-09 Thread Jesse Erlbaum
Hi Cees -- One thing I am still waiting on before I go ahead is a response from Jesse for his blessing to use the CGI::Application namespace for this module. I sent him a private email asking permission a couple of weeks ago, but it probably got lost in the multitude of mail he must get.

[cgiapp] CGI - mod_perl

2004-02-09 Thread Bob Hicks
Saw this on the newgroups and thought of the recent discussion about making CGI-App mod_perl friendly. Maybe it will give ideas. http://perl.apache.org/docs/1.0/guide/porting.html - Web Archive:

Re: [cgiapp] Planning next CGI::App release

2004-02-09 Thread David Naughton
Excellent discussion these past few weeks! I've done much thinking about similar issues, i.e. regarding Apache::Request and new directions for C::A. I'll share my thoughts below. First, thanks to Jesse and everyone who has contributed to C::A. For the last couple of years, I've been using C::A

RE: [cgiapp] Planning next CGI::App release

2004-02-09 Thread [EMAIL PROTECTED]
Hi all. I chose to jump in here because I like much of what Stephen says. I especially agree that C::A should not impinge on people's Other Ways To Do It. For me, C::A is best where it makes the fewest assumptions. Firstly... Let me say that this is one of the first lists I've been