tracingplane-java icon indicating copy to clipboard operation
tracingplane-java copied to clipboard

Java implementation of the Tracing Plane -- Baggage Contexts and Execution-Flow Scoped Variables

Results 26 tracingplane-java issues
Sort by recently updated
recently updated
newest added

Need a spec so that other people know what to implement if they wanted to integrate tracingplane into other languages.

Split out compiler as a separate repo from the java library

### README markdowns in root and project subdirs: - Readmes for root project and all subprojects. Figure out appropriate way of presenting the information. - Tracingplane organization documentation - Directory...

For child data with index < 15, it is cheaper to inline the child as a data atom.

A bag could predefine the point at which overflow is acceptable, so that the bag itself can overflow without causing all subsequent bags to overflow To achieve this, baggage buffers...

Bag options could be specified as a separate child bag rather than in the header. This would be better for supporting changes to the options (eg, if you want to...

One-of fields are useful, especially for use cases like supporting 64/128 bit IDs

In the current implementation, users manually manipulate object fields, because that was quicker to implement. Ideally, it should be more protobuf-style, with getters, setters, and existence checkers. This will also...

Volatile fields are fields that we only want one side of a branch to ever see. When we branch a context, only one side of the branch will get the...

Bags should support transient fields. Transient fields are omitted during serialization; that is, they only live within a single process. Transient fields should behave like other fields -- eg they...