On Wednesday, 2002-09-25 at 10:41:19 -0400, valerian wrote:
BTW, anyone know if Perl 6 will free unused memory? From what I
understand, right now it just allocates as needed, but never gives any
back to the OS when it's done... (ie, when some function ends)
Even if Parrot (the perl 6
Hi Kyle,
There are a few performance penalties when using Apache::Registry:
* Scripts are compiled at first request instead of server start unless you
use something like Apache::RegistryLoader. So, the first request per
child
will be a little bit slower and you don't get to share memory
Hi Ged,
Thanks for replying. I hope you had a good time in my old country :-)
You probably saw the reports on the news about roads being washed away
by the rain in Sevilla. I went on a motor-cycle. Camping.
Mmm... Doesn't sound like the perfect vacation. I'm glad you made it back
:-)
On Tue, Sep 24, 2002 at 08:03:56PM -0700, Kyle Oppenheim wrote:
There are a few performance penalties when using Apache::Registry:
* Scripts are compiled at first request instead of server start unless you
use something like Apache::RegistryLoader. So, the first request per child
will be a
There are a few performance penalties when using Apache::Registry:
* Scripts are compiled at first request instead of server start
unless you
use something like Apache::RegistryLoader. So, the first
request per child
will be a little bit slower and you don't get to share memory
Hi Ged,
Sorry it took a long time to reply. Been to Spain.
Thanks for replying. I hope you had a good time in my old country :-)
If you're writing new code then I would recommend writing handlers and
avoiding Apache::Registry altogether.
I had been thinking about whether to do this. Why
Hi Francisco,
On Tue, 24 Sep 2002, Francisco Corella wrote:
Thanks for replying. I hope you had a good time in my old country :-)
You probably saw the reports on the news about roads being washed away
by the rain in Sevilla. I went on a motor-cycle. Camping.
If you're writing new code
If you're writing new code then I would recommend writing handlers and
avoiding Apache::Registry altogether.
I had been thinking about whether to do this. Why do you
recommend avoiding
Apache::Registry? Is there a performance penalty for using it?
We sometimes use Apache::Registry
Hi Francisco,
Sorry it took a long time to reply. Been to Spain.
On Fri, 13 Sep 2002, Francisco Corella wrote:
I believe calling Apache::exit doesn't prevent the log phase from
being run for the request, does it?
That's the way I understand it.
You recommend using 'return' rather than
Hi there,
On Wed, 11 Sep 2002, Francisco Corella wrote:
The Modules book by Lincoln Stein and Doug MacEachern (pp.464-465)
says that Apache::exit() can be used to halt script execution
without terminating the process and without logging an error.
Ask yourself why you want to call an exit()
"Terminating requests and processes..." that alsodiscusses the
need to use Apache::exit() instead of Perl's buit-in exit().
However, the Apache documentation itself does not
mention an exit() function.Neither "perldoc Apache" nor the documentation
at http://perl.apache.org/docs/1.0/ap
11 matches
Mail list logo
