You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Adam Kurland <Ad...@biospace.com> on 2002/08/29 18:41:26 UTC

RE: tomcat log says HTTP/1.0? HTTPClient

This is a great library.  We have used it in production (life science
research) code for about a year; never had any problems with it.

We even use in a situation in which a servlet creates multiple threads, each
using a connection object from the this library at the same time. 

Just remember that you generally never want to call disconnect(), and that
it pools connection objects to the same server:port for you so that you dont
have to.

And, of course, don't forget to place a copy of the jar file inside the
webapps/<your-app>/WEB-INF/lib directory!

-Adam


-----Original Message-----
From: veton.kosovali@belgacom.be [mailto:veton.kosovali@belgacom.be]
Sent: Thursday, August 29, 2002 5:05 AM
To: axis-user@xml.apache.org
Subject: RE: tomcat log says HTTP/1.0?


What about the HTTPClient from http://www.innovation.ch/java/HTTPClient/ ?

Veton.

-----Original Message-----
From: Brian Ewins [mailto:Brian.Ewins@btinternet.com]
Sent: 29 August 2002 1:42 PM
To: axis-user@xml.apache.org
Subject: Re: tomcat log says HTTP/1.0?


Steve Loughran wrote:
> I would not advise anyone to use HttpURLConnection in production code.
...
> like I said, I would not advise anyone to use HttpURLConnection in
> production code.
> 
> -Steve
> 
> ps, did I mention, I would not advise anyone to use HttpURLConnection in
> production code :)
> 

So any idea when there will be a full release of Jakarta's HttpClient 
then? ;) seriously I've not found an http client that doesnt have bugs. 
For example, we needed to use PUT requests, and the jakarta HttpClient 
hangs doing a PUT request when talking to Tomcat 3.2 (see 
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11653) - this was a 
showstopper for us[1]

Do you have any suggestions for http client libs?

Cheers,
	Baz

[1] yes I know I should just submit a patch, the fix I suggest in the 
bug report is trivial; but for production we needed to know that the fix 
would still be there in the official release.

**** DISCLAIMER **** 
"This e-mail and any attachments thereto may contain information 
which is confidential and/or protected by intellectual property 
rights and are intended for the sole use of the recipient(s) named above. 
Any use of the information contained herein (including, but not limited to, 
total or partial reproduction, communication or distribution in any form) 
by persons other than the designated recipient(s) is prohibited. 
If you have received this e-mail in error, please notify the sender either 
by telephone or by e-mail and delete the material from any computer. 
Thank you for your cooperation."