On Fri, 19 May 2000, David Larkin wrote:
I require a large array of ints in a real application, just stripped
problem down to bear bones for demo.
Is your array sparse by any chance? If not your modperl daemon is going to
get _much_ larger after you populate that array. If it's sparse,
"Jeffrey W. Baker" wrote:
On Thu, 18 May 2000, brian moseley wrote:
On Thu, 18 May 2000, Autarch wrote:
pretty slow if you build a string using .= instead of using
smarter methods, like pushing strings onto an array and then
joining it.
You tried to sell me that when I was at CP,
"Bruce W. Hoylman" wrote:
"Gunther" == Gunther Birznieks [EMAIL PROTECTED] writes:
Gunther This first criteria seems a tad odd to me. What business
Gunther scenario is there for this?
The framework is to support an intranet time tracking application. The
business rules of the
Hello,
I have stumbled upon an issue with Apache::ASP !--#include virtual--
directive. Included files do not seem to be able to access the same scope
of variables. I am using the following test program:
File 1.inc:
!--#include virtual="2.inc"--
% $test .= '1'; %
p$test = %=$test%/p
File
Use file includes. virtual includes are meant to execute
anything and include its output, and is handles by Apache::SSI
outside of Apache::ASP. File includes will be executed as perl
asp subroutines in the same perl namespace as the
including script.
-- Joshua
- Original Message -
From: Randy Kobes [EMAIL PROTECTED]
Sent: Saturday, May 20, 2000 05:50
Subject: Re: mod_perl 1.24, nmake test causes Apache Win32 to crash.
| On Sat, 20 May 2000, Thomas wrote:
|
| hi,
| I've run into some oddities..
| running nmake test causes to seriously
Hi there,
On Fri, 19 May 2000, David Larkin wrote:
Can anyone help explain why PERL gives such a large memory
footprint advise how to get around it.
In addition to the other suggestions, you might want to try
use integer;
in the bits of your Perl code that manipulate integers.
I guess
:
: On Wed, 17 May 2000, Peter Haworth wrote:
:
: Drew Taylor and I are about to write a subclass of Apache::Request
which
: includes form element generation methods, a la CGI.pm. The current
: favourite
: name is Apache::Request::Forms, but we'd like to know if anyone has a
: better
:
[EMAIL PROTECTED] (G.W. Haywood) wrote:
Hi there,
On Fri, 19 May 2000, David Larkin wrote:
Can anyone help explain why PERL gives such a large memory
footprint advise how to get around it.
My general philosophy (well, at least in these matters) is that large
chunks of reference data should
Matt Sergeant writes:
On Fri, 19 May 2000, David Larkin wrote:
I require a large array of ints in a real application, just stripped
problem down to bear bones for demo.
Is your array sparse by any chance? If not your modperl daemon is going to
get _much_ larger after you populate that
On Sat, 20 May 2000, Joshua Chamas wrote:
Use file includes. virtual includes are meant to execute
anything and include its output, and is handles by Apache::SSI
outside of Apache::ASP. File includes will be executed as perl
asp subroutines in the same perl namespace as the
including
Philip Mak wrote:
I see. There are two problems that I have with file includes though:
(1) I cannot specify a file's location relative to $ENV{'DOCUMENT_ROOT'}.
(2) I cannot specify a file's location relative to the directory the
current file is in.
For #1, I want to do something
On Sat, 20 May 2000, Joshua Chamas wrote:
!--#include virtual="/code/header.asp"--
!--#include virtual="/code/footer.asp"--
For #1, know includes will be picked up from your Global directory,
so you can use that repository to share includes, instead of some
DOCUMENT_ROOT location. You
My apache dies about 30% of the time when handling any mod_perl request
that requires XML::Parser. Any other page (even pages that use
mod_perl) are 100% ok.
Are there any known issues with this (besides the requirement for
--disable-rule=expat)? This all worked fine with perl 5.005_03 +
| Well, I would like to suggest that you consider including !--#include
| virtual-- in the Apache::ASP distribution, so that included files use the
| same namespace. It doesn't make sense logically that include virtual
| behaves differently from include file (other than the way the
|
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
16 matches
Mail list logo
