RFE: Provide mechanism to allow request transmission and response reception to
be performed independently
---------------------------------------------------------------------------------------------------------
Key: HTTPCLIENT-854
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-854
Project: HttpComponents HttpClient
Issue Type: Improvement
Components: HttpClient
Affects Versions: 4.0 Final
Environment: All
Reporter: Mike Cumings
Priority: Minor
The HttpClient API currently provides for the execution of a request via the
HttpClient.execute(...) methods. These methods all send the request and then
block until the response has been received. This precludes the user of the API
from being able to send the request, perform some additional work, then come
back and block on the request. This style of processing is very desirable for
implementation of HTTP-based protocols such as Bidirectional-streams Over
Synchronous HTTP (BOSH). This capability is also closely related to
HTTPCLIENT-258, support for HTTP 1.1 pipelining.
The current code base (4.0) currently utilizes
org.apache.http.impl.client.DefaultRequestDirector.execute(...) to transmit
requests. This method contains a retry loop which blocks on and then examines
the response from the remote server. When success is detected, it cleans up
and returns the response instance. Requests are sent using an
HttpResponseExecutor instance. These classes support the ability to separately
doSendRequest() and doReceiveResponse().
Please expose the ability to leverage this functionality outwith the retry loop
but including the existing routing and authorization capabilities, where
possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
