Based on the recent URI discussion, and some other points, it strikes me
that we could take a little more credit for the work that has gone into
HttpClient.
On the HttpClient home page
(http://jakarta.apache.org/commons/httpclient/index.html) four RFCs are
listed.
Given all the discussion
I was always under the impression that the
Sun's Brazil small footprint HTTP stack is a
fast implementation in Java.:
http://research.sun.com/brazil/
One could also go beyond Java (e.g. libwww
or LibWWW or ...)
Otis
On Thu, 30 Jan 2003, Mike Moran
([EMAIL PROTECTED]) wrote:
Eric
Hi,
Based on the Http-client library a WebDAV API was developed (Jakarta slide).
There are plans to implement JSR 147 (a standard Delta-V API) based on this
implementation (currently not finally confirmed).
Best regards,
Juergen
-Original Message-
From: Mike Moran [mailto:[EMAIL
All good points. I had not yet had a chance to update those documents.
Its great to have input from everyone as the content is the hardest part.
I created a bug report for it and am refrencing back to this mail thread.
http://issues.apache.org/bugzilla/show_bug.cgi?id=16625
BTW: anyone can
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12244.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
7) About Mikes idea for having two different classes for stream
posting and parameters posting. I don't really like what that does to
the public interface. Its already fat when it comes to parameters,
and conceptually it is just a POST method.
Here is another idea. Using streams is the
