commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samuel Cheung <SChe...@Novarra.com>
Subject RE: HTTP Clients Vs URL class
Date Wed, 01 May 2002 00:32:52 GMT
Thanks. Does HTTPClient currently support HTTP Persistent Connection?
Caching? File Compression?

Thanks again.
Sam
-----Original Message-----
From: Waldhoff, Rodney [mailto:rwaldhof@us.britannica.com]
Sent: Monday, April 29, 2002 12:10 PM
To: 'Jakarta Commons Developers List'
Subject: RE: HTTP Clients Vs URL class


> One think I know is HTTP Clients supports Cookie. What are other
advantages?

HTTP Client provides significantly more wire-level control over the HTTP
transaction. If you just want to grab content from some URL, then the
java.net.* package may suffice. If you're writing an HTTP client (like
Slide, or Latka, or a SOAP client, etc.) and you begin to have an opinion
about how the transactions are handled, what information gets sent, etc.,
you quickly run into the limitations of the java.net package.

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message