You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2015/04/22 12:39:58 UTC
[jira] [Commented] (HTTPASYNC-91) Http Pipelining is limited to two
(2) requests, then acts synchronous.
[ https://issues.apache.org/jira/browse/HTTPASYNC-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506803#comment-14506803 ]
Oleg Kalnichevski commented on HTTPASYNC-91:
--------------------------------------------
Are you actually sure the client blocks after two requests? The client starts processing response messages as they come, not after sending the whole batch. If the server responds almost immediately this is how message exchanges are likely to look like.
Oleg
> Http Pipelining is limited to two (2) requests, then acts synchronous.
> ----------------------------------------------------------------------
>
> Key: HTTPASYNC-91
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-91
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.1-beta1
> Reporter: Anders Jönsson
> Labels: HttpAsyncClient, HttpPipelining
>
> When issuing pipelined (list of) http requests only the two first requests are actually sent in an asynchronous way. After the two first, all requests are sent synchronously, i.e. a response is awaited before sending the next request. Like this:
> Request ->
> Request ->
> ->Response
> ->Response
> Request ->
> ->Response
> Request ->
> ->Response
> etc.....
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org