Broadcast contexts may be marshalled and transmitted across process boundaries.
Broadcast contexts may be marshalled and transmitted across process boundaries. Finagle clients typically marshal the current context state for outbound requests; Finagle servers receive marshalled contexts and restore them before dispatching a new request.
Thus broadcast contexts are transmitted throughout an entire request tree, so long as the protocols involved support marshalled context values.
Executes fn
with all Finagle contexts cleared.
Executes fn
with all Finagle contexts cleared.
This should be used when Finagle needs to execute work that is not request scoped but may be triggered by something that is part of the request. For example, processing a user request may create a "background Future-loop" which should not capture these request scoped values.
Local contexts have lifetimes bound by Finagle server requests.
Local contexts have lifetimes bound by Finagle server requests. They are local to the process.
com.twitter.finagle.context.Contexts that are managed by Finagle.