Michael Becke wrote:
[snip]
I've been looking into this a little more and I'm actually not sure if
AutoCloseInputStream should close the stream or not. I vaguely
remember when this was first written and the various interactions are
quite complex. In most cases the AutoCloseInputStream is n
2) From a connection standpoint, if the new url is to the same
protocol://host:port then I would expect that the connection be
reused for performance purposes. If not, then a new connection has
to be established and the old one should probablly be closed. But
the call to recycle() will releas
On Sunday, February 2, 2003, at 04:08 PM, Jeffrey Dever wrote:
The idea of recycling methods is good, but at the moment, its not very
useful. Consider the following use case:
1) User needs to make a bunch of GETs as efficiently as possible
2) All the resources that they want to get are full s
The idea of recycling methods is good, but at the moment, its not very
useful. Consider the following use case:
1) User needs to make a bunch of GETs as efficiently as possible
2) All the resources that they want to get are full string urls
3) In a loop, iterate over the list of resources and do