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
As part of Tracing would it be possible to connect all the message calls on a socket to a single context object?
I've been trying to do it myself but I'm really struggling with the context object, it doesn't really behave how I would expect it to.
I also use custom events which are only passed the message data and not a context object.
Essentially what I'm hopping for is a long running trace from which all subsequent calls are logged against and ended when the socket itself disconnects.
At the moment what I'm trying is to co-opting the authentication method and use it to create a new context object. Which I then attach to the socket for subsequent messages to use when making sub calls rather than directly via the broker attached to the Socket IO service.
The text was updated successfully, but these errors were encountered:
As part of Tracing would it be possible to connect all the message calls on a socket to a single context object?
I've been trying to do it myself but I'm really struggling with the context object, it doesn't really behave how I would expect it to.
I also use custom events which are only passed the message data and not a context object.
Essentially what I'm hopping for is a long running trace from which all subsequent calls are logged against and ended when the socket itself disconnects.
At the moment what I'm trying is to co-opting the authentication method and use it to create a new context object. Which I then attach to the socket for subsequent messages to use when making sub calls rather than directly via the broker attached to the Socket IO service.
The text was updated successfully, but these errors were encountered: