Yes, it does fix the problem. Thanks for the help. I remember reading that we
need to consume the entire response body (error or no error) so that connection
can be used (on the Sun side). It is confirmed here.
As far the second question about why HttpCore than HttpClient 3.1; I guess it
is
On the HttpComponents front page it says:
Jakarta HttpComponents project is charged with developing and
maintaining Commons HttpClient. Commons HttpClient 3 series will be
maintained until Jakarta HttpClient 4 is deemed stable enough to
supersede it for use in production.
This text is
On Thu, 2006-11-09 at 08:07 +0800, [EMAIL PROTECTED] wrote:
Yes, it does fix the problem. Thanks for the help. I remember reading that we
need to consume the entire response body (error or no error) so that
connection can be used (on the Sun side). It is confirmed here.
As far the second
I am new to HttpCore and using 4.0 Alpha 2 version. I am trying to connect a
server and request more than one pages from that server using the same
connection. My goal is to reuse socket so that no new socket is opened on the
Http client for the subsequent requests to the same server and port.
On Thu, 2006-11-09 at 04:46 +0800, [EMAIL PROTECTED] wrote:
I am new to HttpCore and using 4.0 Alpha 2 version. I am trying to connect a
server and request more than one pages from that server using the same
connection. My goal is to reuse socket so that no new socket is opened on the
Http
