David Daney wrote:
As I threatened last week, I made some major changes to the
gnu.java.net.protocol.http package. ...
The current version reads the entire body of a HTTP response in to a
memory buffer (ByteArrayResponseBodyReader) and if user code needs the
content it gets a
David Daney wrote:
You would probably have a better chance if you threw out all the
inetlib classes and started from scratch with a pull-based client.
What are you talking about? I am not using inetlib.
The gnu.java.net.protocol.http package is the inetlib HTTP client.
I do agree with
Chris Burdess wrote:
David Daney wrote:
You would probably have a better chance if you threw out all the
inetlib classes and started from scratch with a pull-based client.
What are you talking about? I am not using inetlib.
The gnu.java.net.protocol.http package is the inetlib HTTP
As I threatened last week, I made some major changes to the
gnu.java.net.protocol.http package. The patch is probably not in its
final form, but I thought I would post it to see what the reaction to it
is. At a minimum I would update the copyright dates.
The current version reads the entire
