Adrian Cole 77e9328e12 Ensures Span.timestamp/duration are not reported on remote spans ...

This ensures spans that have remote set to true don't send
Span.timestamp/duration.

In the RPC span model, the client owns the timestamp and duration of the
span. If we were propagated an id, we can assume that we shouldn't
report timestamp or duration, rather let the client do that. Worst case
we were propagated an unreported ID and Zipkin backfills timestamp and
duration.

See https://github.com/openzipkin/openzipkin.github.io/issues/49

2016-11-07 06:59:17 -08:00

..

src

Ensures Span.timestamp/duration are not reported on remote spans

2016-11-07 06:59:17 -08:00

.google

update to s-c-build 1.0.2.BUILD-SNAPSHOT and add .google to s-c-s-zipkin

2015-06-01 11:33:56 -06:00

pom.xml

Updated version to 1.2.0

2016-11-02 13:58:40 +01:00