[sorry for length, I've been wanting to ask this for a while :)]
Hello,
I'm a bit new to coding with mod_perl (and I _am_ new to this list),
and I have a question. :) I have it set up now where my default page
is index.pl, and I've got some other links (e.g. contact/about/faq)
that are
On Mar 27, 2006, at 10:06 PM, Foo Ji-Haw wrote:
Apache::Reload doesn't always work too. two scenarios
...
I use Apache2::Reload myself for my development box. There's an
extra scenario you missed out:
1. If you change the inheritance of the package, you'll get an
error too.
But having
Hey Carl,
The only place where forking is useful is where you want something to
continue processing after sending the response back to the client.
You can achieve the same effective result by calling
$r->child_terminate()
(assuming your using pre-fork). The currently running child exits at
th
Apache::Reload doesn't always work too. two scenarios
...
I use Apache2::Reload myself for my development box. There's an extra
scenario you missed out:
1. If you change the inheritance of the package, you'll get an error too.
But having said that, I find Apache2::Reload very handy for easy
Thanks guys - this is helpful.In reality, and running the ways things are, I already need to restart (or ::Reload) to introduce changes (moved to that paradigm last year) -- but I guess that beyond the efficiencies you point out here in using proper API (for handler, print, etc) and the rationale h
I use Image::Imlib2 for on the fly image creation and it works fine for me.
After the thumbnails are created, memory is restored to normal size.
Image::Imlib2 is also very vast and easy to code.
For filetypes that are not supported by imlib2, I use imagemagick which is
using some more memory but
we should keep this on-list :)
Clinton Gormley wrote:
>>it ought to work, but it should be setting a per-server cleanup instead of a
>>per-request cleanup. see below.
>>
>
>
> Doh!
:)
>
>
>
>>basically cleanups are performed when memory allocated for different parts
>>of the server lifecyc
i generally don't like to do that in modperl unless i have enough
webservers. i think its a bit of a waste of the mp resource.
i do this:
on upload, generate a thumbnail w/Image:Epeg (which is a super fast
implementation of epeg. previously i compiled my own epeg tools and
the perl mod i
On Mar 27, 2006, at 9:42 AM, Frank Wiles wrote:
Overall great advice in this thread, but I wanted to point out
that with Apache2::Reload this isn't strictly the case. You can
set it to reload certain modules or all without a server restart,
however I personally wouldn't use it in produc
On Mon, 27 Mar 2006 14:08:38 +0100
"Carl Johnstone" <[EMAIL PROTECTED]> wrote:
> The next step from there is not using Apache::Registry at all, but
> putting mod_perl handlers into their own modules/packages. However
> there's more of a change here to other ways of working - for example
> you need
Instead of using MP2 syntax, etc, we're still using:
print "Content-type: $type\n\n";
print "blah";
and in sending redirects, we use stuff like:
print "Location: $url\n\n";
Is this a problem or is it just bad style?
What reasons are there to continue our port to use the correct r
Can you fork off a separate process to do this (that will die once it is
completed)?
The only place where forking is useful is where you want something to
continue processing after sending the response back to the client.
You can achieve the same effective result by calling $r->child_terminate(
On 3/27/06 6:21 AM, "Tom Schindl" <[EMAIL PROTECTED]> wrote:
> Please note that this is not only true for Image-Creation but also if
> you are restoring large string contents in a variable (e.g. after
> processing a file-upload).
>
> Tom
>
> Frank Maas wrote:
>> Tom,
>>
>>
>>> As a sidenote
Please note that this is not only true for Image-Creation but also if
you are restoring large string contents in a variable (e.g. after
processing a file-upload).
Tom
Frank Maas wrote:
> Tom,
>
>
>>As a sidenote often it is not really desired/dangerous to run image
>>creation as a mod_perl hand
Well image creation in mod_perl is not a bad idea if you ensure that the
process is killed after it succeeded a certain memory. The problem in
case of mod-perl/httpd is that that if every httpd-process is eating 20
MB of space only because you have created once an image. You must ensure
that only v
Tom,
> As a sidenote often it is not really desired/dangerous to run image
> creation as a mod_perl handler because of the nature of perl, memory
> allocated once is never freed until the process shutdowns or is killed
> (by your Apache::SizeLimit handler).
Ah, you got me worried there... How in
Hi,
this is a mod_perl forum please ask perl questions on perl-monks or any
other perl-support forum and if it is a perlbug file a bug using perlbug
to p5p.
Tom
cyg_win_user wrote:
> i m trying to read environment variable in perl using
>
> $OSTY = $ENV{OSTYPE};
> this will return os ty
i m trying to read environment variable in perl using
$OSTY = $ENV{OSTYPE};
this will return os type as "linux" or "solaris". but when i try for cygwin
it returns empty string. is the some other syntax of way of finding value of
env variable in cygwin
--
View this message in context:
htt
18 matches
Mail list logo
