It would be interesting for systems not supporting websockets to be able to send a "LISTEN_OSC" to the OSCQuery server, mentionning CLIENT_IP,CLIENT_PORT and CLIENT_PROTOCOL (TCP/UDP), that would make the server create an OSC connection to this IP:PORT and send value and structure feedback through this OSC stream.
This is less secure as the websocket if the OSC is in UDP, but that would allow for more flexibility on how to implement bi-directionnal communication with more "simple" systems
It would be interesting for systems not supporting websockets to be able to send a "LISTEN_OSC" to the OSCQuery server, mentionning CLIENT_IP,CLIENT_PORT and CLIENT_PROTOCOL (TCP/UDP), that would make the server create an OSC connection to this IP:PORT and send value and structure feedback through this OSC stream.
This is less secure as the websocket if the OSC is in UDP, but that would allow for more flexibility on how to implement bi-directionnal communication with more "simple" systems