[OSC_dev] Application Profiles

[Nicholas J Humfrey]

> 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.



nick.