[ http://issues.apache.org/jira/browse/HTTPCORE-11?page=comments#action_12433177 ] Roland Weber commented on HTTPCORE-11: --------------------------------------
Hi Oleg, (1) passing HttpContext as parameter is fine. The further it spreads, the better I like it. Removing the connection argument is also fine. (2) I'm not so sure about. It's something that might be useful for HttpAsync, and I think it's a bit early to introduce a dependency on HttpClient there. Let me think about this for a while. cheers, Roland > Provide generic server and client connection primitives that can work with > arbitrary HTTP data receivers and transmitters. > -------------------------------------------------------------------------------------------------------------------------- > > Key: HTTPCORE-11 > URL: http://issues.apache.org/jira/browse/HTTPCORE-11 > Project: HttpComponents Core > Issue Type: Improvement > Components: HttpCore > Affects Versions: 4.0-alpha2 > Reporter: Oleg Kalnichevski > Assigned To: Oleg Kalnichevski > Fix For: 4.0-alpha3 > > Attachments: conn.patch, httpclientconn.patch, > httpcore-abstractconn.patch > > > Provide generic server and client connection primitives that can work with > arbitrary HTTP data receivers and transmitters. The default connection > primitives in their present form are tightly coupled with the java.net.Socket > class. There are cases when the underlying I/O transport is based on > different media (MINA transport, NIO channels) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
