You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 3, 2020. It is now read-only.
Currently in v1 the service/topic handlers work solely based on the binary data arriving from the network (broadcast, request, event). The issue is, that in the current API it is impossible to transfer the request context from the service layer up to the handler (think in terms of the contextual logger).
In the Java binding, the logger context can be carrier to the handler through the ThreadLocal, so it is covered, however Go doesn't have the notion of goroutine state, so maybe the binary blobs should be wrapped in some contextual struct containing the logger too.
Dunno, will have to ponder on this a bit.
The text was updated successfully, but these errors were encountered:
Currently in v1 the service/topic handlers work solely based on the binary data arriving from the network (broadcast, request, event). The issue is, that in the current API it is impossible to transfer the request context from the service layer up to the handler (think in terms of the contextual logger).
In the Java binding, the logger context can be carrier to the handler through the ThreadLocal, so it is covered, however Go doesn't have the notion of goroutine state, so maybe the binary blobs should be wrapped in some contextual struct containing the logger too.
Dunno, will have to ponder on this a bit.
The text was updated successfully, but these errors were encountered: