On 13/01/06, Roland Weber <[EMAIL PROTECTED]> wrote: > Hi sebb, > > > JMeter can download embedded resources (images) etc referenced in a > > page, and these may well be from a different host:port. > > > > If the next page is from the original host, would it not be better to > > keep the original connection for further requests? > > That's what the connection manager is there for. A connection that is > returned to the connection manager is "free", but not necessarily closed. > The HostConfiguration passed to the CM when requesting a connection > indicates the host:port to which the connection will be targetted, and > the connection manager can then choose an open connection to that host. > The SimpleConnectionManager has nothing to choose from, of course. > > HttpClient will detect whether the connection returned by the CM is an > open connection to the target host:port and re-use it if so. Otherwise, > the HttpConnection object will be pointed to the appropriate host:port > and a new (socket) connection is opened. >
Yes, but as you say, the Simple Manager has but one connection to play with. The MultiThreaded Manager presumably has as many as are allocated to it, but seemed like overkill for a single thread, and I did not want JMeter to block if there were no connections free. Nor does JMeter need connection idle checking. I already had code to keep track of connections/host, so I just adapted this to keep track of clients for each host. Perhaps I could have used the MultiThreaded Manager instead. S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
