Christian Weiss

This library only defines the interfaces and I don't think interfaces can be marked as `Serializable` so this is something that each tracer would have to implement. Also, AppDomains are...

Please file any objections until May 2nd - I'll merge afterwards if there's none.

Found my own concerns 😄 and filed them here https://github.com/opentracing/specification/issues/116. I'll put this on hold until that issue is resolved.

I will add this if there's going to be a new release - see #128. There's not much going on here anymore as most work is done in the newer...

In .NET, most new libraries/frameworks provide instrumentation hooks via an observer pattern through a type called [`DiagnosticSource`](https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.DiagnosticSource/src/DiagnosticSourceUsersGuide.md). Having a "no-tracer"-check (e.g. `tracer.isEnabled()`) would allow us to not even create a...

In that case I would like to remove the "BINARY"-carrier code from the library for now to not block a 0.9.0 release. We'll look into this later. Is this ok...

I removed the binary format for now. We'll put it back once we know the correct type.

#50 will add the binary format using `Stream` as a type constraint. I don't know if that's correct so if anyone has any complaints don't hesitate to comment here or...

Alright, then let's leave the binary format out for now. It's better to add it once we have a clear understanding of how it should be used. I've seen that...

In terms of the specification, the more interesting question for me is the contract of this API: * Should it be possible to store just one span in the context?...