We're implementing a REST client on JRE 1.4.
Seems two good options for a client REST framework are HttpClient and HttpUrlConnection.
Is there a reason to use HttpClient over the JRE's HttpUrlConnection?
A:
In my experience HttpClient is slightly easier and more intuitive to use than using HttpUrlConnection, but I think it's a very subjective decision and YMMV.
Aditya
2009-11-16 01:02:44
+1
A:
I'd go with the JRE version just so I would have one less dependency to ship around.
Eric
2009-11-16 01:04:31
This comparison looks kinda dated
jitter
2009-11-16 01:10:58
Some of us don't have the luxury of using the latest versions of **anything** :-(
Michael Rutherfurd
2009-11-16 02:39:29
A:
The HttpUrlConnection is easy to handle. REST implementations are quite simple.
Although you must consider the whole environment about this implementation and check what will work better for you.
jonaspp
2009-11-16 02:25:03
+2
A:
The Restlet Framework also has an API which works both server-side and client-side. We support pluggable client connectors, leveraging HttpURLConnection or Apache HTTP Client or our own internal HTTP client.
Our ClientResource class provides a higher level HTTP client API, with features like automatic redirection, transparent conversion between objects and representations, content negotiation and more.
Best regards,
Jerome Louvel
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
Jerome Louvel
2009-11-20 15:42:40
@Marcus: Yes, it does, I'm using Restlet's client right now in Java 1.6 and it's a dream. (We have it configured to sit on top of Apache HTTP Client, which is much better than java.net.HttpUrlConnection.)
Jim Ferrans
2009-11-25 09:53:05
+1
A:
I'll give you a single, concrete reason to favour Apache's HTTPClient over the JDK implementation: The JDK's HttpUrlConnection doesn't support timeouts, Apache's HTTPClient does.
Applications should always have the ability to set timeouts when calling into other systems (databases, remote services, your own server backend, ...).
hbunny
2009-11-22 10:04:01
+1
A:
I would recommend Jakarta Commons HTTP Client over java.net.HttpUrlConnection as it is more mature and has a richer feature set. For example you can ask it to set up multi-threaded connection pool (see MultiThreadedHttpConnectionManager), and it has full support for all the HTTP methods (GET, PUT, POST, DELETE, OPTIONS, TRACE).
Jim Ferrans
2009-11-25 09:50:27
A:
... httpclient does not support kerberos/ntlm authentication for proxies etc... java's httpurlconnection will do authentication out of the box...
helmut
2010-03-30 08:03:42