[
https://issues.apache.org/jira/browse/HTRACE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264892#comment-14264892
]
Elliott Clark commented on HTRACE-54:
-------------------------------------
Pretty sure that HTraced already does keep-alive's.
http://golang.org/pkg/net/http/#Server.SetKeepAlivesEnabled
{quote}
SetKeepAlivesEnabled controls whether HTTP keep-alives are enabled. By default,
keep-alives are always enabled. Only very resource-constrained environments or
servers in the process of shutting down should disable them.
{quote}
> htraced should do keepalive
> ---------------------------
>
> Key: HTRACE-54
> URL: https://issues.apache.org/jira/browse/HTRACE-54
> Project: HTrace
> Issue Type: Improvement
> Reporter: stack
>
> htraced needs http keepalive otherwise clients need to put up a connection
> each time they want to send spans via REST.
> Batching should ameliorate the lack of keepalive but better for the client to
> stream the spans as they are received and pass them off to the htraced daemon
> near-immediately rather than have to put up a connection each time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
