Re: counting the number of connections?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 5, 2009, 17:00 UTC
Message-ID: <alpine.DEB.1.00.0903051758440.6524@intel-tinevez-2-302>
In-Reply-To: <87ab80j649.fsf@krank.kagedal.org>

Hi,

On Thu, 5 Mar 2009, David Kågedal wrote:

Show 25 quoted lines

> Tay Ray Chuan <rctay89@gmail.com> writes:
> 
> > some time ago I noticed curl doesn't remember your credentials (apart 
> > from those it can get from ~/.netrc), and very recently there was an 
> > thread on repeated prompting for credentials while pushing to https.
> >
> > I've written a simple patch series, which allows git to play nice
> > without curl_multi. That is, git uses a single persistent connection
> > throughout.
> >
> > However, I'm at a loss at how to test for this. How does one count the
> > number of connections made during the lifespan of a program's
> > execution? So far, I've been relying on my firewall log (Comodo on
> > windows). Perhaps there a more operating system/software-agnostic
> > method to do this?
> 
> You could set up a single-use tcp forwarder which will make any second
> connection fail. Using socat, for instance:
> 
>   $ socat tcp-listen:2222,bind=localhost tcp:my.server:22 &
>   $ nc localhost 2222
>   SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1
>   ^C
>   $ nc localhost 2222
>   localhost [127.0.0.1] 2222 (?) : Connection refused

AFAICT Ray wants to provide tests for Git's test suite, and introducing socat as a dependency for our tests does not really fly all that well.

But IIRC somebody convinced Ray that it is better to require a new-enough cURL version so that the patch becomes moot itself.

Ciao, Dscho