Re: Status of ra_serf

And, with Apache, remember that the Apache developers can't tell you
if there is a memory leak or not. All of the standard modules may be
fine, without a leak, but then add another module (mod_perl, mod_php,
etc), that allow people to run their own logic within the same
process, and a leak is absolutely possible.

Ryan

On 2/19/06, Peter Samuelson <peter@p12n.org> wrote:
>
> [Phillip Susi]
> > Right, but is there any reason for the server not to allow an
> > unlimited number of requests per connection rather than hanging up
> > after a limit?
>
> According to apache docs a long time ago, each process only answers N
> requests, then it dies, in order to mitigate against any memory leaks
> that might happen to exist. It may be that N is too small in today's
> or tomorrow's world of deeply pipelined RPC-like requests.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFD+A1pXk7sIRPQRh0RAhISAKCfz8GD9D5isKJYotBOpeXv8znsOACgjEj5
> GHNglkWlNO8w3Tg/wkuKLSQ=
> =7kB8
> -----END PGP SIGNATURE-----
>
>
>

--
Ryan Bloom
rbb@apache.org
rbb@rkbloom.net
rbloom@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org