You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Usman Ismail (JIRA)" <ji...@apache.org> on 2011/04/27 17:25:03 UTC
[jira] [Resolved] (THRIFT-1153) HttpClient does not specify the
connection close parameter
[ https://issues.apache.org/jira/browse/THRIFT-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Usman Ismail resolved THRIFT-1153.
----------------------------------
Resolution: Not A Problem
You are right the underlying transport layer is providing persistent connectivity so this makes sense. I was using similar code for an async http client implementation and it was causing problems there.
> HttpClient does not specify the connection close parameter
> ----------------------------------------------------------
>
> Key: THRIFT-1153
> URL: https://issues.apache.org/jira/browse/THRIFT-1153
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.6.1, 0.7
> Reporter: Usman Ismail
> Assignee: Usman Ismail
> Labels: c++, http, httpclient, network
> Fix For: 0.7
>
> Attachments: ConnectionClose.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> THttpClient.cpp builds a header fort he http request in the flush method but it does not set the Connection: Close header which means the client wait for EOF until the server closes the socket. This will slow all requests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira