Thanks for your reply Oleg. You wrote:
> Is there a reason for using such an outdated version of HttpClient? We have started to use it when it came out, and did not have a direct need to upgrade. But we will plan for that. > > As far as i understood the execute(), it blocks until the whole stream > is > > read from the socket. Is that not the case? Can the performance of > writeTo() > > be in some way depending on the network? > > Absolutely. Smaller messages may fit into the network buffer in their > entirety. Larger messages most likely are transmitted with several > packets. Delivery of those packets can be affected by network > nstability or congestion. > >Oleg Of course I am aware of the fact that the network affects the performance of execute(), but I expected all packets to be transferred once execute() returns? My question targets especially the call writeTo(). From what I can see, writeTo() just copies bytes from one place to another, and, in the end, calls the connection manager to release the connection. So can even writeTo() have a varying performance based on the network? Regards Oliver -- View this message in context: http://httpcomponents.10934.n7.nabble.com/responseEntity-writeTo-performance-depending-on-network-tp19194p19203.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
