[
https://issues.apache.org/jira/browse/HTRACE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263977#comment-14263977
]
stack commented on HTRACE-30:
-----------------------------
The issue 'make htraced more RESTful' has me thinking we should be checking for
content-type */json before parsing the request body as json. Or for now we are
just JSON all the time? We ever going to take something else? Your cmd should
set content-type of */json?
This is required?
63 if b[0] != DOUBLE_QUOTE {
64 return errors.New("Expected spanID to start with a
string quote.")
Where we going to write up the REST spec? We need to start a markdown doc
describing the REST htraced digests? Or that later after REST vocabulary
settles? Probably better if the htraced serves up a page of the REST vocabulary
if you pass ?help or something?
+1 on v2. Lets get it in. Need it to test client.
> Add writeSpan REST verb to htraced
> ----------------------------------
>
> Key: HTRACE-30
> URL: https://issues.apache.org/jira/browse/HTRACE-30
> Project: HTrace
> Issue Type: Improvement
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-30.001.patch, HTRACE-30.002.patch
>
>
> Add a /writeSpan REST verb to htraced so that we can create spans, as well as
> query them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
