Possibly. I think the idea is to keep in mind that people who are reading
cgi_to_mod_perl are total newbies. Not only that, but many are planning on
staying total newbies forever; they don't care about what mod_perl is
actually for (or actually can do). I think that the cgi_to_mod_perl
manpage should be targeted at that kind of perspective...
Issac
Internet is a wonderful mechanism for making a fool of
yourself in front of a very large audience.
--Anonymous
Moving the mouse won't get you into trouble... Clicking it might.
--Anonymous
PGP Key 0xE0FA561B - Fingerprint:
7E18 C018 D623 A57B 7F37 D902 8C84 7675 E0FA 561B
----- Original Message -----
From: "Perrin Harkins" <[EMAIL PROTECTED]>
To: "Issac Goldstand" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, March 14, 2001 9:30 PM
Subject: Re: cgi_to_mod_perl manpage suggestion
> On Wed, 14 Mar 2001, Issac Goldstand wrote:
> > I still think that the above line is confusing: It is because
mod_perl is
> > not sending headers by itelf, but rather your script must provide the
> > headers (to be returned by mod_perl). However, when you just say
"mod_perl
> > will send headers" it is misleading; it seems to indeicate that mod_perl
> > will send "Content-Type: text/html\r\n\r\n" all by itself, and that
> > conversely, to disable that PerlSendHeaders should be Off.
>
> Would it help if it said "PerlSendHeader On makes mod_perl act just like
> CGI with regard to headers"?
> - Perrin
>
