OSCQueryProposal
OSCQueryProposal copied to clipboard
Vidvox
Draft of a proposal for an OSC Query Protocol
I would suggest to change the described behaviour of what happens after receiving a LISTEN command from clients. I think the clients that sends a LISTEN command will be interested...
I would be great to be able to have a "METADATA" object to put metadata when giving info, so the client can adapt depending on different project-specific parameters (OS or...
Hi! In my work with [TWO](www.thewizardofosc.com), I've come across the issue of sub-sections of the OSC address spaces of large applications, very often being identical, because they correspond to instances...
In the examples there is a method with the OSC type `"i[ff]i"` I'm not sure if that describes a type that has 1 int followed by a fixed sized array...
In the `Optional Attributes` `VALUE` section there is a bullet point with this text: > If a query is performed for the "VALUE" attribute, but the OSC method does not...
Hey, thanks for this reference ! I guess a common case would be to just want to listen to any value change from the server, not only from external OSC...
It would be interesting to be able to choose what type of message is sent through the websocket. Encapsulating OSC and sending through websocket may not be the easiest thing...
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...
in the examples: ```Some queries may return empty objects- "/baz" is a pure container object- it doesn't accept any OSC messages, so it doesn't have a type:``` Why doesn't `get...
Is there any reason that an `OSC method` actually has to be a leaf? The proposal references the [OSC spec](http://opensoundcontrol.org/spec-1_0) and provides this bullet point: >An OSC server's OSC Methods...