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
Is your feature request related to a problem? Please describe.
Hello guys,
I was wondering if there is a way of identifying which instance of the websocket client is populating the message callback method, I would like to create these web socket client instances dynamically, so they might change over the time.
Describe the solution you'd like
The message or event callback methods should also include a reference to the instance client that fired those callbacks
Describe alternatives you've considered
Creating an array/vector pairing both the instance of the callback method and the client instance
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hello guys,
I was wondering if there is a way of identifying which instance of the websocket client is populating the message callback method, I would like to create these web socket client instances dynamically, so they might change over the time.
Describe the solution you'd like
The message or event callback methods should also include a reference to the instance client that fired those callbacks
Describe alternatives you've considered
Creating an array/vector pairing both the instance of the callback method and the client instance
The text was updated successfully, but these errors were encountered: