[OSC_dev] Application Profiles

[salsaman at xs4all.nl]

On Sun, December 21, 2008 11:38, Nicholas J Humfrey wrote:
>> I am profoundly sorry, but #reply is not a valid OSC name
>
> Perhaps that was a deliberate decision to use a reserved character to
> make it part of the protocol layer, rather than an application.
>
>
>> I would love to use "#info", etc but it's not allowed by the spec or I
>> am missing something important here.
>
> If '#' remains a reserved character for application developers then it
> means they can't incorrectly use '#' where it has a special meaning.
>
>
>> The current things we have sorted out on
>> openmediacontrol.wetpaint.com/ are (maybe there is not a total
>> agreement on everything):
>>
>> 1. Get answers to queries back:
>> /reply_to <port>
>>
>> The reply is "/omc/player/vlc", "/omc/rubyk" = namespace. The IP can
>> be retrieved from the originating UDP packet.
>
> I really don't like this. It adds the concept of a connection/session.
> What is wrong with just sending the reply straight back to the socket
> that sent the query? Being connectionless is a big feature of OSC.
>
>

Then you just send /reply_to <port> where port is also the sending port.

Or we could say that <port> is optional, and if ommitted, replies are sent
to originating port/host.

Why remove the flexibility that someone might want to do otherwise ?

And why are you not commenting on the wiki ? I am assuming if nobody
comments there then there is a general agreement.


Gabriel.


>
> nick.
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>