Add OSCQuery-style live updates: same-port WebSocket + LISTEN/IGNORE #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds OSCQuery-style live value updates by serving HTTP and WebSocket on the same port and supporting LISTEN/IGNORE with binary OSC over WebSocket, as in the OSCQuery proposal.
Changes
aiohttpis installed, HTTP and WebSocket run on the same port (HOST_INFOws_port= HTTP port). Falls back to a separate WebSocket port if onlywebsocketsis available.{"COMMAND": "LISTEN", "DATA": "/path"}(andIGNORE) to subscribe; the server streams binary OSC packets whenupdate_value(path, value)is called (requirespython-osc).LISTENandPATH_CHANGEDto EXTENSIONS when using the combined server.aiohttpfor same-port server; existing optionalpython-oscandwebsocketsunchanged.Backward compatibility
aiohttpis not installed, behavior matches the previous implementation (separate WebSocket port, JSON push).OSCQueryServiceconstructor orupdate_value().Tested