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
Firstly I would like to thank you for the multi-sessions feature.
Unfortunately the multi session capability is not quite thread safe and one can end up sending API calls using a header from another session. Which seems to be due to the shared session_stack.
As a workaround one can use use threading lock to limit one vspk call at a time, but this blocks until the response to the call is received. To minimise the blocking time, I am currently using asynchronous calls and only lock the "call send" ( maily the API call header generation I suppose ) .
It would be nice if the multi-session synchronous calls could be used thread safely.
Thank you very much.
The text was updated successfully, but these errors were encountered:
Hello,
Firstly I would like to thank you for the multi-sessions feature.
Unfortunately the multi session capability is not quite thread safe and one can end up sending API calls using a header from another session. Which seems to be due to the shared session_stack.
As a workaround one can use use threading lock to limit one vspk call at a time, but this blocks until the response to the call is received. To minimise the blocking time, I am currently using asynchronous calls and only lock the "call send" ( maily the API call header generation I suppose ) .
It would be nice if the multi-session synchronous calls could be used thread safely.
Thank you very much.
The text was updated successfully, but these errors were encountered: