hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Weber (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HTTPCORE-11) Provide generic server and client connection primitives that can work with arbitrary HTTP data receivers and transmitters.
Date Fri, 08 Sep 2006 20:41:22 GMT
    [ http://issues.apache.org/jira/browse/HTTPCORE-11?page=comments#action_12433492 ] 
            
Roland Weber commented on HTTPCORE-11:
--------------------------------------

Hi Oleg,

the absence of an open(...) method in HttpClientConnection means that HttpAsync can no longer
use the interface, but has to reference an implementation class or an extended interface.
This could only be acceptable as a short-term intermediate step until we re-introduce some
version of open(...) with HTTPCORE-8. I'm not sure there is a point in going this intermediate
step, but since I won't find time to fix HttpAsync for another week, it doesn't matter much.
The question really is whether I can fix HttpAsync before or after we've found a solution
to HTTPCORE-8.

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-2.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: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org


Mime
View raw message