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
That is, can it be used concurrently from multiple threads?
Or should there be something that queues calls to it, like reads/writes to TCP handle?
I've actually already implemented a queueing mechanism, and now just feeling a bit stupid as from looking at source code it does look thread safe, and queueing requests just makes performance worse...
The text was updated successfully, but these errors were encountered:
@kazu-yamamoto this is a real issue - this function is not thread safe and cannot be used concurrently.
I currently use queueing that makes sure there are no concurrent calls to this function, but probably it should be thread safe given how API is designed.
epoberezkin
changed the title
[Question] Is sendRequest function passed to the client thread-safe?
[Limitaion] sendRequest function passed to the client is NOT thread-safe – it cannot be called concurrently
Feb 21, 2023
That is, can it be used concurrently from multiple threads?
Or should there be something that queues calls to it, like reads/writes to TCP handle?
I've actually already implemented a queueing mechanism, and now just feeling a bit stupid as from looking at source code it does look thread safe, and queueing requests just makes performance worse...
The text was updated successfully, but these errors were encountered: