On 13/01/06, Roland Weber <[EMAIL PROTECTED]> wrote: ... > > > > I've now had a look at the code. > > > > SimpleConnectionManager only has a single connection, and does not > > seem to block (unless closing the connection can do so). > > > > At present we use a single connection per host per thread - there may > > be several different host:port combinations in a single thread. > > > > So I guess we could use a separate instance of HttpClient per "thread-host". > > I don't understand what you are trying to do. HttpClient is synchronous: > a thread will block until the response for a request has been received.
Agreed. > If your thread has to connect to different hosts, it should still be > connected to a single host (or not at all) at any point in time. Hence, > the single connection "managed" by the SimpleConnectionManager can be > used for one host:port after another. Agreed. > What am I missing? 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? I imagine this is closer to how browsers work? Sebastian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
