The problem is that java.net.HttpURLConnection will not open up more
than 2 physical connections to the same destination host (it's an RFC
spec thing that they comply with .... I can't remember which RFC it's
been so long since I looked at it) .... however Apache HttpClient has
no such limitations .... so if you are going to have many threads in
a single woa or many different instances on the same machine making
the connections, then HttpClient will not bottleneck due to the
global 2 connection limit in the underlying implementation.
On Mar 1, 2007, at 9:37 AM, Asa Hardcastle wrote:
I've heard great things about apache's httpclient, so it is
probably a good choice. However, if you want to stick with J2SE
and you're using 1.5, you can use java.net.HttpURLConnection. SSL
is easy, and you'll be dealing with a stream. This class finally
allows reliable setting of the read and connect timeouts.
asa
On Mar 1, 2007, at 9:24 AM, Robert Walker wrote:
WOHTTPConnection should work fine for this, as long as you don't
need SSL. If you want a more flexible solution that does fully
support SSL connections I would recommend the Apache HttpClient,
which is what I use with great success.
You can find HttpClient here:
http://jakarta.apache.org/commons/httpclient/
On Mar 1, 2007, at 5:19 AM, WIESEN Bruno wrote:
Re Hello,
I used to implement SOAP in order to send and receive XML
information to a server...But now I must use another type of
sending....
I have to send XML information to : http://xxxx:8080/xxx
What can you advise me?
I try with WOHTTPConnection and WORequest...Is it a good thing??
Thank you.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
