That patch is just plain wrong. Usable as a stopgap, but not something to be
committed.
I was dead tired last night and had to crash after some minimal testing.
I'll get the stuff cleaned back up.
Jeff: what is going wrong for you with Ryan's new patch?
Cheers,
-g
On Tue, Jan 09, 2001 at 03:25:
[EMAIL PROTECTED] writes:
> rbb 01/01/09 11:28:38
>
> Modified:.configure.in
>.APRVARS.in configure.in
> Log:
> Fix a compile break with the new APR libtool setup. Basically, we are
> using a libtool library from MM, but it isn't getting linked
> Hiya,
> This is part 1 of a multi-part patch to include APR_DECLARE(foo_t)
> statements for all external APR functions. To aid verification (and reduce
> the risk of a massive screw-up) I'm
> sending a seperate patch for each
> functional group starting with apr_pools. I'll wait for approva
OK, so I've reworked the patch and it doesn't break anything so do people
want to see it or shall I just commit?
Basically we now cache the APR_ values and you can set the
TCP_CORK/TCP_NOPUSH via the apr_setsocketopt call. apr_getsocketopt works
fully as well (using the cached values...)
david
On Mon, Jan 08, 2001 at 10:30:32PM -, David Reid wrote:
> Folks,
>
> This is a small patch that's very much a starting point. Basically
> following Deans suggestion we should be tracking what options we have set on
> a socket and using the cached information to avoid system calls. I've used
