On Thu, 21 Dec 2000, Doug MacEachern wrote:
On Thu, 19 Oct 2000, Chris Nokleberg wrote:
Following up on my post on this subject a couple of months ago, here is a
proof-of-concept drop-in replacement for Apache::Registry that eliminates
the "my() Scoped Variable in Nested Subro
In case your script makes some db changes "by accident"--if you don't do
an explicit rollback or commit at the end, the uncommitted changes will
hang around, and the next request may end up committing those changes
unwittingly. I rollback at both the beginning and the end of all requests,
just to
FYI this is not mod_perl related.
You'll want the IO::String package. If the perl function you
are calling is just printing to the default filehandle (which I'm guessing
it does), you should be able to just 'select' the IO::String object:
my $str;
my $str_fh = IO::String-new($str);
my
d to
bring the user back to the same box.
--Chris
On 22 Nov 2000, David Hodgkinson wrote:
Chris Nokleberg [EMAIL PROTECTED] writes:
Of course, the front-end proxy servers don't have mod_perl, so the
TransHandler would have to be written in C (?). Does anyone know of any
existing code that does
Most of our pages are served by identical load-balanced boxes, and it
doesn't matter which box serves what.
However, a few special pages store a lot of per-user session data. Instead
of burdening our db machine to store this data, I would like to use the
filesystem. This requires that for these
On Sun, 21 May 2000, G.W. Haywood wrote:
You might think that it serves little purpose for a light Apache
server simply to pass all requests from a socket through to a heavy
mod_perl server, only then to receive the reply and pass it back to
the socket.
But you don't usually know what
I was rereading
http://perl.apache.org/guide/scenario.html#Buffering_Feature
and was surprised to find:
"Therefore if you don't use mod_proxy and mod_perl send its data
directly to the client, and you have a big socket buffer, the
mod_perl process will be released as soon as the last
to add a section on the best way to simplify or eliminate the need
to modify the conf file for each new handler? Perl sections, etc.?
Thanks,
Chris
--
Chris Nokleberg + Internet Sports Network, Inc.
[EMAIL
-
Chris Nokleberg + Internet Sports Network, Inc.
[EMAIL PROTECTED] + http://www.SportsRocket.com/
for now?
(using Apache 1.3.9, mod_perl 1.21)
Thanks,
Chris
--
Chris Nokleberg + Internet Sports Network, Inc.
[EMAIL PROTECTED] + http://www.SportsRocket.com/
10 matches
Mail list logo
