ContextsContainer for the request id obtained by
RequestIdProvider
Reads any contexts written back from the server by calling
ContextsContainer.consumeBidirectionalContextsFromResponse(ContextKeySupplier)
ContextsContainers for servers.String context to this request scope.ContextsContainer.addContext(String, Object, ContextSerializer) is unidirectional i.e.ContextsContainer with those
contexts.ContextsContainer instances as channel attributes.ContextsContainer objects between threads.PipelineConfigurator for the context module.ContextsContainerContextsContainer.serialized.serialized.ContextSerializer for BiDirectional contexts that requires information about the
direction of flow (i.e.DirectionAwareContextSerializer to provide consistent behavior for callers who are
unaware of this interface and treat all serializers as ContextSerializerContextsContainer.addContext(String, String) or ContextsContainer.addContext(String, Object, ContextSerializer)
The context could have been set in a different service and transferred here on the wire.ContextsContainer.addContext(String, String) or ContextsContainer.addContext(String, Object, ContextSerializer)
The context could have been set in a different service and transferred here on the wire.ContextsContainer to a fresh client request.ContextKeySupplier) that is to be used to transfer the
request identifier from one machine to another.PipelineConfigurator to configure an HttpClient with the context handling.ContextKeySupplier that reads context keys from HTTP headers.RequestIdProvider for HTTP protocol.PipelineConfigurator to configure an HttpServer with the context handling.Callable into a closure so that it can capture the contexts as it exists when this
Callable is created and use it during the context's execution, which happens in a different thread.Runnable into a closure so that it can capture the contexts as it exists when this
Runnable is created and use it during the context's execution, which happens in a different thread.ContextKeySupplier which is backed by a MapBiDirectional contexts.ContextKeySupplier for the passed message that is being read.ContextKeySupplier for the passed message to be written.requestId.requestIdkeySupplier or context to see if there is a request Id already defined for this
request.contextName added previously in this request scope via
ContextsContainer.addContext(String, String) or ContextsContainer.addContext(String, Object, ContextSerializer)
The context could have been set in a different service and transferred here on the wire.ContextsContainer are specific to a request and in order to uniquiely identify a request
we require an identifier.RxClient and RxServer objects which are context aware.toSerializetoSerializeRequestCorrelator that fetches ContextsContainer and request Identifer from
ThreadLocal variables.