On 7/12/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
a) the tie be global pre-fork
b) the tie be post-fork
c) there be no tie whatsoever , and somehow a connection is made
using the API at the beginning , and everything just uses the library/
api methods
~b + ~c
Open
paul trader wrote:
> however, there seems to be no apache/build.pm module anywhere in
> /usr/lib/perl5.
>
> am i missing something here?
I normally build my own Perl/mod_perl on my systems since RH ships a threaded
Perl which I never need and which is slower than a Perl built with just the
defau
all - i've just set up a new fedora 7 installation on my laptop. when
trying to build an rpm for libapreq2, it dies telling me that
apache::test.pm is not found. after retrieving apache::test from cpan and
trying to build an rpm for that, it tells me that apache2::build is not
found. cpan
Could you elaborate on this?
I'm a bit unclear:
are you suggesting
a) the tie be global pre-fork
b) the tie be post-fork
c) there be no tie whatsoever , and somehow a connection is made
using the API at the beginning , and everything just uses the library/
api methods
?
m
On 7/12/07, Nils Kaiser <[EMAIL PROTECTED]> wrote:
To achieve full performance, I read
that it better to tie the berkeleyDB once and reuse the handle for each
request, i.e. having the tie command outside of the mod_perl handler.
Yes. If you really are concerned with performance, don't use the
Hello,
in a former post, I was investigating the use of berkeleyDB and mod_perl
to cache calls to a web service.
We now have a running prototype. To achieve full performance, I read
that it better to tie the berkeleyDB once and reuse the handle for each
request, i.e. having the tie command o
