Paul Draper

I don't understand why the Tracer interface needs to be Closeable. Tracer implementations, I understand. But not the Tracer interface. Isn't a Tracer only destructed by its creator? And its...

There's a singular code example and it references an implementation. The only plausible case for not having the concrete importation seems to be "reflection", thus making the proposal the equivalent...

OpenTracing is some high-level concepts, with a collection of standards. **Language** Currently, the standards are facades for each language: Java, Go, JS, etc. **Inter-process propogation** We could say that we...

> OpenTracing began life (even before it had its current name) as an attempt to standardize parts of Span representation. Side note: OpenTracing has a leg up on any other...

I'm just not sure why we have to throw up our hands in the HTTP case. One easy approach to key-value encoding is UTF-8 percent-encoding, like ``` X-Opentracing: key1=value1 X-Opentracing:...

Option 3 seems appropriate. But the documentation goes further and talks vaguely about what key and values can and can't be used. It's a partial regression in the desire to...

Actually, I've reconsidered. It's still a sticky point, but it seems reasonable.

I've added an implementation of CPS-style JS span activation https://github.com/opentracing/opentracing-javascript/pull/113. For example, the implementation using the [Zone](https://github.com/domenic/zones) TC39 proposal: ```ts const propertyKey = 'opentracing'; const zoneName = 'opentracing'; interface PropertyData...

@alloy, that is of great interest, thanks! Until last month, Datadog used a CPS-style CLS library. I didn't know they had replaced it. The current imperative RFC can be implemented...

> As far a closing the scope, the approach we took currently is to automatically close the scope only when the entire asynchronous context has ended, including any child contexts....