[
https://issues.apache.org/jira/browse/HTTPCLIENT-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Weber updated HTTPCLIENT-258:
------------------------------------
Fix Version/s: (was: 4.0 Final)
5.0
In order to enable pipelining in HttpClient, the connection management API and
therefore HttpClient would have to be remodeled to a two-phase allocation of
connections. First the connection is allocated for sending the request, then
released for sending (unless there is an expect-continue handshake) and
allocated for receiving the response. To avoid pointless sending of requests,
the connection re-use strategy should make partial decisions based on the
request alone, for example if there is a "connection: close" header.
Authentication and secure tunnels add another layer of complexity to this
problem.
Many of the problems will have to be addressed in HttpAsync. Once we've learned
how to handle pipelining there, we can attempt to bring it into the HttpClient.
> RFE: Implement HTTP 1.1 Pipelining
> ----------------------------------
>
> Key: HTTPCLIENT-258
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-258
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Affects Versions: 2.0 Beta 2
> Environment: Operating System: All
> Platform: All
> Reporter: Ortwin Glück
> Priority: Minor
> Fix For: 5.0
>
>
> Pipelining is currently employed by Mozilla based browsers, which are reported
> to gain some performance from it.
--
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]
