[OSC_dev] Application Profiles

[adrian at cnmat.berkeley.edu]

> A lot happened today, so let's clarify some things and post some more
> questions...
>
> 1. just reply back to port from message header
>
> Using the sender's port and IP from the UDP header is great in theory,
> but in practice I could not make it work:
>
> Impossible to define the output port of "udpsend" in Max/MSP (I
> receive the data in rubyk at "50867", replies just get lost). I could
> not create an "udpreceive" with port "50867" either (there is probably
> something already bound to this port, says max).
>
> All in all, we need at least a dictionary of "received from port" =>
> "send to port". So "/reply_to 5005", is needed.

some nasty security problems with this approach to consider.

> a. use a special syntax for "meta" methods (get information, type, etc
> = equivalent of ".h" files in C)
>
> The existence of this special syntax should not make it too heavy to
> process incoming messages. I propose Gabriel's idea of using
> "/some/url(info)", because the trailing ")" is easy to detect and
> means "hey osc processor, this is a special url". It also conforms to
> OSC spec.

Have you considered the approach proposed by the Jamoma folk?

http://www.jamoma.org/papers/jamoma-nime2008.pdf