Re: mod_perl advocacy project resurrection

[Ben Cottrell]

On Tue, 5 Dec 2000 12:40:47 -0800 (PST), brian moseley wrote:
> On Tue, 5 Dec 2000, Dave Rolsky wrote:
> 
> > Each has its advantages.  Perl is good for real
> > programmers who are going to write code to actually
> > solve a problem.  Java is good for monkeys who think
> > that buying a $100k app server and tweaking it via a
> > monolithic API will give them what they want.
> 
> c'mon dude, offer something constructive to the thread or
> stay out of it.

Except that he's absolutely right.

I have personal experience -- my company is ripping out its elegant
mod_perl based architecture and replacing it with *cough* the
j-word *cough*.

mod_perl is the superior technology, hands down. This is coming from
someone who's an avowed perl hater, too. I loathe perl itself, but
have to admit that mod_perl, when you compare it to the alternatives
in the dynamic-web-content space, just plain rules.

Just one example... my company ran into a bug in mod_perl a while ago...
so what did we do? we fixed it, and submitted a patch. If we'd been
using the J-word, we'd have been stuck. Tell me one big-name app server
that's written in C and that'll let you download the source and fix
bugs.


Kinda hard to laugh hangin' there in one o' them "virtual machines", Rob...


~Ben
 (this message comes guaranteed to offend absolutely everybody in
 some fashion or other)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: return from nested functions

[Ben Cottrell]

On Wed, 1 Nov 2000 11:37:00 -0800 (PST), "Paul J. Lucas" wrote:
>   If I'm a few levels deep into function calls, I'd liek to be
>   able to do something like "return SERVER_ERROR" and have the
>   entire call stack unwind and the current request stopped.

Will something like this do what you need?

~Ben



eval
{
get as many levels deep into functions as you want
...
...
...
die("SERVER_ERROR");
...
...
...
};

$the_error = $@;
if ($the_error)
{
warn("Unwound stack because of $the_error");
}

Re: Question on Apache::Compress

[Ben Cottrell]

On Mon, 2 Oct 2000 15:28:09 -0400 (EDT), kevin montuori wrote:
>   bc> Static .html files aren't compressed at all (but do come through
>   bc> as text/html).
>   
>   do you have 
> 
> SetHandler perl-script
> 
>   in there somewhere?

Kevin,

This fixes static html completely! It's compressed, and also comes
through as text/html. Thanks very much!!

perl scripts are still coming through as compressed (which is good)
text/plain (which is bad). Umm. Who has control over the content-type?
I thought the perl script itself did (i.e. print "Content-Type: text/html\n\n")
but I can't find that anywhere in our perl code (I'm not the one who writes
the scripts, so I don't know the code... I'm just responsible for apache).
Is there any other possible way the content type would have been getting
set, previously, that might be broken with the addition of Apache::Compress?

Thanks again :-)

~Ben

Question on Apache::Compress

[Ben Cottrell]

Hi,

This is in regards to Ken Williams' Apache::Compress module (announced
here on August 22).

I've installed it, along with zlib, Compress::Zlib, and Apache::Filter,
and am having a couple of issues getting it running -- wondering if anyone
has any clues.

perl is version 5.004_04, apache is 1.3.6, mod_perl is a dev snapshot from
February 4 of this year (1.21 something), with one local bug fix. Yes, I
know all of those are out of date, to varying degrees :-) We've had some
of apache stability issues at my company, and sometimes we've downgraded,
or avoided upgrading, to avoid whack-a-mole bug stomping. mod_perl was
compiled with EVERYTHING=1.

For perl, we have:
PerlModule Apache::Filter

SetHandler perl-script
PerlSetVar Filter on
# the following line is what used to be here, and worked great,
# but we're changing it to put compression in.
# PerlHandler Apache::Registry
PerlHandler Apache::RegistryFilter Apache::Compress
PerlFixupHandler Apache::SizeLimit
PerlSendHeader On
...

And for static pages, we have:
PerlModule Apache::Compress

Options Includes FollowSymLinks ExecCGI
Header set Pragma no-cache
PerlHandler Apache::Compress
...

Perl scripts compress perfectly, except come through as text/plain
instead of text/html.

Static .html files aren't compressed at all (but do come through as
text/html).

Any clues?

Thanks!

~Ben