Re: HTTPClient vs java.net.URLConnection

[Paul Hendley - Sun Microsystems]

I've just recently started using HTTPClient with struts on the webserver and it 
seems pretty reliable.  Although I haven't really pushed it much, it was easy to 
get up and running and I haven't found any real issues with it.  (I think I had 
one issue but can't remember what it was...I guess it wasn't that bad.)  

Also, the feature set seemed to be well thought out and organized.

As an example, HTTPClient made it easy to mess with cookies using the provided 
methods.

Anyways, some of my next tasks should be to start pushing it a bit harder.  
We'll have to see what happens then.
 
-Paul




        Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
        list-help: <mailto:[EMAIL PROTECTED]>
        list-unsubscribe: <mailto:[EMAIL PROTECTED]>
        list-post: <mailto:[EMAIL PROTECTED]>
        Delivered-To: mailing list [EMAIL PROTECTED]
        From: Maya Muchnik <[EMAIL PROTECTED]>
        X-Accept-Language: en
        MIME-Version: 1.0
        To: [EMAIL PROTECTED]
        Subject: HTTPClient vs java.net.URLConnection
        Content-Transfer-Encoding: 7bit
        X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
        
        Hi,
        Does anyone use HTTPClient? What do you think about it? I have got this 
link several
        minutes ago.
        As its document said, in HTTPClient you can set timeout for response, 
pipelining of
        request. Source code is available. It includes the source code for 
parsing the
        multiPartRequest.
        
        HTTPClient can find at:
        http://www.innovation.ch/java/HTTPClient/