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
Often it is required to cache a full websocket message before processing it. This buffer needs to be associated to an individual client to avoid race conditions. Currently I need to use std::map to map the client id to a buffer. It would be faster and easier if there was a void * in AsyncWebSocketClient which could be used for any purpose the user of this library wants.
Many other libraries do the same thing, either providing a pointer to the callback or allowing to store data on the object.
Another option would be a new variant of AsyncWebSocketClient which does the buffering internally and only calls the callback once the message is completely received.
The text was updated successfully, but these errors were encountered:
Often it is required to cache a full websocket message before processing it. This buffer needs to be associated to an individual client to avoid race conditions. Currently I need to use std::map to map the client id to a buffer. It would be faster and easier if there was a void * in AsyncWebSocketClient which could be used for any purpose the user of this library wants.
Many other libraries do the same thing, either providing a pointer to the callback or allowing to store data on the object.
Another option would be a new variant of AsyncWebSocketClient which does the buffering internally and only calls the callback once the message is completely received.
The text was updated successfully, but these errors were encountered: