[
https://issues.apache.org/jira/browse/HTRACE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503272#comment-14503272
]
stack commented on HTRACE-150:
------------------------------
Where is the 'protocol' described?
Client goes hrpc if HTRACE_WEB_ADDRESS is set in cnf at HTRACE_HRPC_ADDRESS ?
You want that?
28 METHOD_ID_WRITE_SPANS = iota ? What is 'iota' (other than...)
Skimmed the rest. Seems good. I think you will likely change the protocol as
you make progress w/ the client as you trip over issues so +1 on committing
this for now (with some doc on how the protocol works and how to set config to
enable this REST alternative).
> htraced: add HRPC endpoint for writeSpans
> -----------------------------------------
>
> Key: HTRACE-150
> URL: https://issues.apache.org/jira/browse/HTRACE-150
> Project: HTrace
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-150.001.patch
>
>
> We should add a non-HTTP way of adding spans to htraced, for greater
> efficiency. This would also help minimize dependencies in the C client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
