[OSC_dev] oscit registration complete !

[salsaman at xs4all.nl]

On Fri, January 30, 2009 22:23, Joseph Malloch wrote:
>>>
>>> /register                                                - register
>>> this
>>> client for replies in bi-
>>> directional context
>>> /register <port>                                  - register client on
>>> same host (address/port not
>>> in datagram)
>>> /register <ip address> <port>         - register client on remote host
>>> (address/port not in datagram)
>>
>>
>> Fine with me, in fact that's how we already have it
>> (http://wiki.integralive.org/lib:server).
>
> Also quite similar to the stuff we use here, except our system is
> distributed so after negotiating for unique identifiers and ports a
> device sends:
>
> /device/registered <ip address> <port> <deviceClass> <numInputs>
> <numOutputs>
>
> this is multicast on the "admin bus"
>
> Joseph Malloch
> Input Devices and Music Interaction Laboratory
> Schulich School of Music - McGill University
> email: joseph.malloch at mcgill.ca
> web: http://www.music.mcgill.ca/~mallochj
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>



OK, since we all seem agreed on this, at least as a first step, I have
added it to the summary page:

http://openmediacontrol.wetpaint.com/page/summary


If we follow the numbering on the page, then the next question is - what
should /register return (if anything), and what should be the format of
the return.


For the latter I would strongly prefer all return values as plain text
(ASCII) for reasons that I have explained already.

Cheers,
Salsaman.
http://lives.sourceforge.net