On Thu, 8 Sep 2005, Jaclyn Whitehorn [EMAIL PROTECTED] wrote:
While there is such a thing as over-simplifying, I really don't see why
TT can't be covered in a page or two. I personally think that the
book should primarily use HTML::Template, since it's (1) integrated,
and (2) EASY. At some
On Tue, 6 Sep 2005, Johan Kuuse wrote:
Plan to mention something about I18N/L10N, generally in web programming
and/or particularly in CGI::Application?
Definitely! Thanks I don't know how I missed that one.
--
Jaldhar H. Vyas [EMAIL PROTECTED]
On Wed, 7 Sep 2005, Jeff MacDonald wrote:
Recently there has been a flourish of writting less code and several
best practices, using Class::DBI and the like.
Will there be a section on this sort of thing ? [Kick my ass if I
missread this anywhere]
Given that Class::DBI is a complex system
Jaldhar H. Vyas wrote:
The reason I split this into two chapters is that CGI::Apps integration
with HTML::Template means you can get an immediate advantage over straight
CGI.pm right away. And although I did use Template Toolkit in my last
project, to be honest it doesn't seem to have huge
Michael Peters wrote:
Jaldhar H. Vyas wrote:
So perhaps I should cover HT::Dot in the introductory chapter, and TT and
the rest in Ch. 12?
I would cover (or mention) TT before HT::Dot. It's much more popular and
a staple in the perl community. I know the boook will target people who
On Sep 8, 2005, at 6:08 PM, Michael Peters wrote:
I would cover (or mention) TT before HT::Dot. It's much more popular
and
a staple in the perl community. I know the boook will target people
who
aren't perl programmers, but it's important to let existing perl
programmers that we're not
On Mon, 5 Sep 2005, Javier Donaire wrote:
I would also add a section to run under FastCGI, because it is less
memory hungry than mod_perl and easier to set up in shared hosting
environments.
Ok good suggestion.
Great book!
Wait till I've written something before deciding :-)
--
Jaldhar
On Mon, 5 Sep 2005, Jason A. Crome wrote:
Why leave testing for the end? Why not strictly leave chapter 13 to
optimization, and start indoctrinating people with testing from the
beginning?
Possibly because, sad to say that's how I usually do it. Though I have
seen the error of my ways.
On Mon, 5 Sep 2005, Andrew Brosnan wrote:
Sounds like the book will focus almost exclusively on running CGIApp as
CGI (rather than under mod_perl).
For the most part yes.
But I would think most developers run
under mod_perl, no?
If you are going to develop specifically for mod_perl, you
If you are going to develop specifically for mod_perl, you should probably
be writing handlers and using the full-fledged power of the Apache API.
Well, mod_perl is not the simplest persistent Perl environment, but
there are times when it's appropriate for running CGI apps, even when
those
On 9/7/05, Michael Graham [EMAIL PROTECTED] wrote:
Most CGI::Application based apps should be able to run fine under
straight CGI, mod_perl Registry, a simple mod_perl handler, FastCGI, and
PersistentPerl (a.k.a. SpeedyCGI).
I think a FastCGI plugin for CGIApp is long overdue. It just needs
Plan to mention something about I18N/L10N, generally in web programming and/or
particularly in CGI::Application?
Regards,
Johan
--
Johan Kuuse
[EMAIL PROTECTED]
Tue Sep 6 22:16:24 2005
-
Web Archive:
Why leave testing for the end? Why not strictly leave chapter 13 to
optimization, and start indoctrinating people with testing from the
beginning?
IMHO, the more people are exposed to testing, the more likely they
are to understand and use it in their own development. By leaving
On 9/4/05 at 7:02 PM, [EMAIL PROTECTED] (Jaldhar H. Vyas) wrote:
A couple of months back we had some discussion on a CGI::Application
book. I think I am ready to get started on this. As a first step to
making a proposal to a publisher[1] here is a synopsis of the books
possible contents.
From: Jaldhar H. Vyas
A couple of months back we had some discussion on a
CGI::Application book. I think I am ready to get started on
this. As a first step to making a proposal to a publisher[1]
here is a synopsis of the books possible contents. This is
just a brain dump so I
BTW, is CAF on the CA website? If not, seems like it should be.
Thanks for the push! I've added it to the Other Frameworks page:
http://cgiapp.erlbaum.net/cgi-bin/cgi-app/index.cgi?OtherFrameworks
It probably should have its own page too - I'll get to that eventually.
Michael
---
A couple of months back we had some discussion on a CGI::Application book.
I think I am ready to get started on this. As a first step to making a
proposal to a publisher[1] here is a synopsis of the books possible
contents. This is just a brain dump so I appreciate any and all comments,
On Sun, 4 Sep 2005 19:02:20 -0500 (CDT), Jaldhar H. Vyas wrote:
Hi Jaldhar
Very nice indeed.
I suggest including a discussion of maintaining state, in this sense:
o While the CGI script is running, it has local memory, accessed via $self -
param(x = $y). When the script exits, this memory is
On Mon, 5 Sep 2005, Ron Savage wrote:
I suggest including a discussion of maintaining state, in this sense:
o While the CGI script is running, it has local memory, accessed via $self -
param(x = $y). When the script exits, this memory is lost forever.
o The CGI script can save state in
On Sun, 4 Sep 2005, Jaldhar H. Vyas wrote:
Ch 1: Common Gateway Interface
What is CGI? Perl good language for CGI. CGI not dead yet. (Advantages
over proprietary methods like java, .net) CGI.pm standard for perl CGI
programming (with example.)
Make sure you know your stuff when you
On Sun, 4 Sep 2005, Sam Tregar wrote:
Make sure you know your stuff when you compare CGI to Java and .NET.
There's nothing like a misinformed advocate to damage the reputation
of a technology. Why am I worried? Most server-side Java and .Net
apps use CGI. Also, Java isn't proprietary in
21 matches
Mail list logo
