Re: Limit Connection Count in Client Side API

On Wed, 26 Feb 2003, Thomas Kriegelstein wrote:

>
>
> Hi,
>
> How can i limit and/or specify the connection count in the client side =
API?
> (org.w3c.www.protocol.http)

It is usually done via some properties (max connetions). However, this
needs to be reworked a bit to give it some pluggable rules to control it,
instead of this fixed behaviour.
In the meantime, you can recompile HttpManager with debug =3D true and se=
e
if it goes over the limit, of it is a problem of connection not perfectly
closed (the JIT sometime defer "real" close of sockets)

 >
> RFC 2616 (HTTP 1.1) Section 8.1.4 states:
> --8<--
> Clients that use persistent connections SHOULD limit the number of
> simultaneous connections that they maintain to a given server. A single=
-user
> client SHOULD NOT maintain more than 2 connections with any server or p=
roxy.
> A proxy should use up to 2*N connections to another server or proxy, wh=
ere N
> is the number of simultaneously active users.
> -->8--
>
> Normally my proxy has one active user (a Mozilla 1.2.1 with HTTP/1.1 to
> proxies enabled) and opens up to 20 connections to my server.
>
> Even if i set the max connection (JigAdmin/http-server/Properties/proxy=
) to 5
> more than 10 show up.
>
> Is there a bug in the client side of jigsaw or have i missed an importa=
nt
> point?
>
> The real reason for this message: I have some protocol like ssl and the
> handshaking while establishing the connection takes much cpu cycles. I =
want
> to reduce the connection count to reduce the overhead.
>
> Ciaou,
>   Thomas
>

--=20
Yves Lafon - W3C
"Baroula que barouleras, au ti=E9u toujou t'entourneras."