On Tue, 9 Jul 2019 at 10:01, thor list <th.list_at_gmail.com> wrote:
> Does O2 not sufficiently solve the query problem? See here:
>
> https://www.cs.cmu.edu/~music/cmsip/readings/o2-web.pdf
Thanks, hadn't seen that information via the other link you shared.
Still, no it doesn't in my opinion -
"Normally, O2 messages do not send replies, and we do not propose any
built-in query system at this time, mainly because queries never
caught on in OSC implementations."
And I don't understand the point of -
"Unlike classic remote procedure call systems implementing synchronous
calls with return values, real-time music systems are generally
designed around asynchronous messages to avoid blocking to wait for a
reply."
So, you have asynchronous RPC! What's always been missing for me in
OSC is an optional sender address (and ID) *in the message header*,
such that you can implement bi-directional messaging and queries and
anything else that needs to know where it's getting the message from
easily. It shouldn't be part of the payload, because that requires
the end point to *have* to know how to handle it, but it would open up
so many more useful things for distributed work.
I also have a distinctly meh response to
https://github.com/vidvox/oscqueryproposal It would be better done
entirely within OSC.
Basically I'd love to expose the entire structure of PraxisCORE hubs
via a standard mechanism rather than having to roll my own protocol on
top of OSC as I am now.
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
PraxisLIVE - hybrid visual live programming
for creatives, for programmers, for students, for tinkerers
www.praxislive.org
_______________________________________________
Livecode mailing list -- livecode_at_we.lurk.org
To unsubscribe send an email to livecode-leave_at_we.lurk.org
Received on Tue Jul 09 2019 - 09:21:01 BST