It always take sometimes to negociate a connection opening between two computers. They must exchange a few packets before the connection is established. The time taken depends, imo, mostly of the round-trip time.
-- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be ----- Original Message ----- From: "Paul" <paul.blommae...@telenet.be> To: "ICS support mailing" <twsocket@elists.org> Sent: Thursday, March 05, 2009 9:48 PM Subject: Re: [twsocket] HttpCli Keep-alive > Hi Francois, > > I think you misunderstood the question. > 3 clients are connected to the same server. > 1 client has a keep-alive connection and the the most part of the job. > Sometimes, 2 other clients have to send or receive additional data. > To keep the server load as low as possible, I'm now testing with a > connection close for those 2 other clients. > My questions is : would there be any speed penalty for the 2 clients that > now use a connection-close instead of keep-alive. > I can't see any difference here, but it's a high speed line. > Maybe there is no difference at all, since the first connection > (keep-alive) > keeps the route open to the server. > It would lower the server load since it doesn't have to send keep-alives > to > the other 2 clients. > > Paul > > > > ----- Original Message ----- > From: "Francois PIETTE" <francois.pie...@skynet.be> > To: "ICS support mailing" <twsocket@elists.org> > Sent: Thursday, March 05, 2009 9:23 PM > Subject: Re: [twsocket] HttpCli Keep-alive > > >>> I have one client that is connected with a keep-alive connection that >>> continuosly sends commands. >>> The other 2 clients send or receive commands when there are command >>> available, but far less frequent than the first one. >>> Is it neccesary to set the connection keep-alive for the other 2 clients >>> ? >>> I'm testing with them without keep-alive and I can see no difference, >>> but >>> it's hard to see here on a 35Mb/s line >> >> There is a tradeof between performance (with keep-alive) and server load >> (much more simultaneous connections with keep-alive). >> The server has always the possibility to close the connection even if >> keep-alive is requested. >> >> -- >> francois.pie...@overbyte.be >> The author of the freeware multi-tier middleware MidWare >> The author of the freeware Internet Component Suite (ICS) >> http://www.overbyte.be >> >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be >> > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be