[ 
https://issues.apache.org/jira/browse/HTRACE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HTRACE-51:
------------------------
    Attachment: 51.txt

{code}
First cut at a receiver for htraced that uses REST.
    Not finished. Was waiting on a write REST verb to finish.
    Missing is the batching up of spans and POSTing to htraced (async).

    Adds new htrace-htraced module intended to house htraced and htraced
    client(s). Moving htraced here will keep htrace-core clean with Interfaces
    and basic implementations only; tooling will be out in other modules.

    Makes jackson a first-class dependency moving it up to top-level pom
    since used by core and htraced modules.

    Adds new receiver, HTracedRESTReceiver, that takes a hostname and port
    for remote htraced daemon and a timeout.

    Adds a non-blocking httpclient used by the receiver to send spans to
    htraced via REST modeled on 
https://github.com/timboudreau/netty-http-client/
    (TODO: Reexamine if could not just include the above client altogether:
    at first blush it had too many dependencies and did more than we need here
    but go look again).

    Non-blocking is probably overkill given it unlikely we'll ever have
    more than a single connection going on and we'll be batching up the
    writing of spans but a nice-to-have.

    TODO: add http keepalive support and optionally compression.
{code}

> htraced java REST client (a.k.a java SpanReceiver for htraced)
> --------------------------------------------------------------
>
>                 Key: HTRACE-51
>                 URL: https://issues.apache.org/jira/browse/HTRACE-51
>             Project: HTrace
>          Issue Type: New Feature
>            Reporter: stack
>            Assignee: stack
>         Attachments: 51.txt
>
>
> Add a java REST client for htraced so we can build a receiver that writes 
> htraced via REST from a java process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to