commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Re: [HttpClient] Retriving an unbuffered stream
Date Mon, 26 Aug 2002 13:44:43 GMT
Jeff Dever wrote:
 > I *really* like the idea of the self closing input stream
...

It's a very good design practice that who gets resources is the owner of 
the resource, so who is the owner of the Socket must close the Socket.

This as a *general* rule.

 > HttpClient has to handle some pretty varied user types, with different
 > needs.
 > 1) User just wants a simple connection to a web server with
 >    as many details hidden from them as possible.
 > 2) User wants to functionally test a web application with
 >    as many details exposed as possible for validation purposes.

It can be possible that a user of a resource delegates something to 
others or to the resource, but it should be explicit.

> If the user sets a timeout and then does not do a read in time, then thats
> up to the user.  It might be some part of the test but they set the
> parameters.  
> 		"with power comes responsibility"

exactly :-)

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
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