[OSC_dev] Application Profiles

[adrian at cnmat.berkeley.edu]

> On Mon, December 22, 2008 14:01, Jamie Bullock wrote:
>> On Mon, 2008-12-22 at 12:21 +0100, salsaman at xs4all.nl wrote:
>> <snip>
>>> >> c. /some/url   ==> get value
>>> > Agree!
>>> >
>>> >> d. /some/url 4 ==> set value
>>> > Agree!
>>>
>>> This is broken as I have pointed out - does not work if get and set
>>> have
>>> different parameters, unfortunately. I showed an example where this
>>> causes
>>> ambiguity.

In our music programming work with OSC we avoid get and set semantics
wherever we can in favor of a stateless approach. Managing states between
two domains is very error prone and hard work.

For example in a video control application I would continuously send OSC
bundles representing the "current state" of the play point and speed for
example and this would be asynchronous to messages from the control
channel going the other way. The stateless approach is usually simpler and
more robust and importantly for music doesn't require a slow variable
latency turnaround of "call response" sequences.