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
Looked at the WebSocketAudioSource class to realise that the server will only support one client at a time. Also leads to this weird (but expected, i guess) behaviour - when two clients connect sequentially, the later one has response offsets that carry over from the first one.
I can see a way to add multi-client support - happy to make a PR - but wondering if this choice is intentional? And if i am missing something?
New here, and really appreciate the detail and thought that has gone into this work already!
The text was updated successfully, but these errors were encountered:
janaab11
changed the title
Support multiple client connections
Support multiple client connections over Websocket
Nov 17, 2024
Looked at the
WebSocketAudioSource
class to realise that the server will only support one client at a time. Also leads to this weird (but expected, i guess) behaviour - when two clients connect sequentially, the later one has response offsets that carry over from the first one.I can see a way to add multi-client support - happy to make a PR - but wondering if this choice is intentional? And if i am missing something?
New here, and really appreciate the detail and thought that has gone into this work already!
The text was updated successfully, but these errors were encountered: