At 10:42 PM 11/19/2000 -0800, [EMAIL PROTECTED] wrote:
>[snip]
>
>Apache::Registry - use it only for backend or lowtraffic sites. It does
>not cache anything, so when you do databases, and files, can be bad to
>horrible to use. Using with small MySQL databases (50,000< records) you
>can get medioc
At 03:04 PM 11/19/2000 -0800, Randal L. Schwartz wrote:
> > "Didier" == Didier Godefroy <[EMAIL PROTECTED]> writes:
>
>Didier> on 11/19/00 4:55 PM, Ime Smits at [EMAIL PROTECTED] uttered the following:
> >> | How do we make sure regular CGI scripts are using mod_perl???
> >> | Is there a way t
On Sun, 19 Nov 2000, E.S. wrote:
> All other things being equal, what's the general performance difference
> between writing your own handlers or using a templating system vs. using
> your scripts under Apache::Registry? I've been running my old CGI scripts
> under Apache::Registry for awhile no
Another learning C book that I think is quite excellent but I keep
forgetting its title everytime this question crops up is:
"Topics in C Programming" by Kochan and Wood.
After doing an excellent exposition of pointers that I have seen in any
book it jumps into topics where most other beginning
Hi,
I know what you're thinking, yet another mod_ssl problem :)
Anyway, I'm trying to run a test (and limited production) server using
mod_perl. I have a great and wonderful mod_perl site working, complete with
Apache::Registry/Apache::Request scripts working (all loaded objects).
My scripts
>> Try getting rid of Perl 5.6 and using 5.005. This has worked for me and for
>> several other folks running other flavors of Unix.
>
> Weird, but compiled 5.6 perl with default options does not mesh well with
> mod_perl, however I run Mandrake Linux, and 5.6 precompiled for this
> platform, se
Hi,
Today I upgraded to Apache 1.3.14, mod_perl 1.24_01, Apache::ASP 1.27, which
seems to work just fine, except that for *each* mod_perl script being
executed I get something like
[Mon Nov 20 05:22:13 2000] [error] [client 192.168.31.31] need AuthName:
/site/gpsmap.plp
in my error.log, however
At 15:10 19/11/2000 -0700, E.S. wrote:
>> on 11/19/00 6:04 PM, Randal L. Schwartz at [EMAIL PROTECTED] uttered the
>> > When you're *really* good with mod_perl, you abandon Apache::Registry
>> > and move up to writing handlers or using embedded templating systems
>> > like EmbPerl, Mason, or Templ
Stas already ran benchmarks. Search the previous posts if he didn't include
them in the guide.
At 03:10 PM 11/19/2000 -0700, E.S. wrote:
> > on 11/19/00 6:04 PM, Randal L. Schwartz at [EMAIL PROTECTED]
> uttered the
> > following:
> >
> > > When you're *really* good with mod_perl, you abandon
> on 11/19/00 6:04 PM, Randal L. Schwartz at [EMAIL PROTECTED] uttered the
> following:
>
> > When you're *really* good with mod_perl, you abandon Apache::Registry
> > and move up to writing handlers or using embedded templating systems
> > like EmbPerl, Mason, or Template Toolkit.
>
Question..
Find the time to READ the documentation
Tonight would be a good nite.
Ruben
http://www.mrbrklyn.com
> At the moment, I'm just trying to get mod_perl to work and have users'
> scripts use it. I haven't had time to read docs on how to use it, only
> enough to get it going.
> Will it speed up
>
> When you're *really* good with mod_perl, you abandon Apache::Registry
> and move up to writing handlers or using embedded templating systems
> like EmbPerl, Mason, or Template Toolkit.
Actually, if your using EMBPERL, why even BOTHER with the CGI interface
at all.
But I think that EMBPERL u
on 11/19/00 6:04 PM, Randal L. Schwartz at [EMAIL PROTECTED] uttered the
following:
> Didier> Can I assume that whenever mod_perl is enabled that all existing perl
> Didier> scripts use it without any modification of any kind?
>
> Not at all. Apache::Registry is a good stop-gap, but you have to
> "Didier" == Didier Godefroy <[EMAIL PROTECTED]> writes:
Didier> on 11/19/00 4:55 PM, Ime Smits at [EMAIL PROTECTED] uttered the following:
>> | How do we make sure regular CGI scripts are using mod_perl???
>> | Is there a way to find out?
>>
>> Check $ENV{MOD_PERL}, it should read somethin
on 11/19/00 4:55 PM, Ime Smits at [EMAIL PROTECTED] uttered the following:
> | How do we make sure regular CGI scripts are using mod_perl???
> | Is there a way to find out?
>
> Check $ENV{MOD_PERL}, it should read something like "mod_perl/1.24".
Can I assume that whenever mod_perl is enabled th
>>> PJ> When I start up apache (apachectl startssl), I get a core dump.
>>> PJ> Attached is an "strace httpd -X" for those of you who find this
>>useful.
>>>
>>> FWIW, I have the same issue also. I noticed it when using CGI::Carp.
>>> My solution was not "use" CGI::Carp; in startup.pl (a real lame
| Is there a way to tell the browser(s) not to make this same substitution
in
| the near future?
| Or, is there a better way to do a one time only redirect from within a
| dynamic page?
I don't expect IE to do anything by the rules, but maybe you can experiment
with sending an explicit Status: 30
| How do we make sure regular CGI scripts are using mod_perl???
| Is there a way to find out?
Check $ENV{MOD_PERL}, it should read something like "mod_perl/1.24".
Ime
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
On 19 Nov 2000, at 9:05, quagly wrote:
> This book looks great! I had seen it before, but assumed that it was all
> C.
>
> Thanks for the tip.
>
> ~quagly
>
I was thinking along the same line. The title of the book doesn't do
it justice. I checked out the book from oreilly's after readin
This book looks great! I had seen it before, but assumed that it was all
C.
Thanks for the tip.
~quagly
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I know this is not directly a mod_perl issue, but I did use mod_perl to
present the issue. . .
So here it is:
When I issue: $r->header_out(Location=>"$dst"),
The browser (IE 5 in my case so far) goes to the fully specified $dst URL.
My problems is that, if the browser attempts to go back to the o
Gunther Birznieks wrote:
> The CGI scripts on your site would not be passed through Apache::Registry
> or Apache::PerlRun, they would run as normal CGIs. No? So that makes sense
> as a motivation to allow mod_perl on a server for content handlers that are
> tightly defined. But don't allow the us
22 matches
Mail list logo
