Re: [liblo] #reply

[Stephen S. <rad...@gm...>]

Yeah I hadn't even realized the #reply functionality was there until
very recently when I was browsing the source code for a different
reason.

I'm watching that discussion on OSC_dev, and I'll be interested in
discussing further development in LibLo, if anything comes of it.
However I'm pretty wary of putting anything in LibLo that isn't in a
standard, since these things may as well be application-dependent if
they're not going to be standardized.

That was also my reason for not immediately accepting the Avahi patch
that someone posted a while ago---I still think it's a good idea, but
I want to make sure it follows some agreement with the rest of the
community.

Steve


On Sun, Dec 21, 2008 at 5:46 PM, Steve Harris
<S.W...@ec...> wrote:
> That's the one.
>
> To be perfectly honest it didn't seem that well thought out, but I
> felt that OSC was really lacking some kind of schema/discovery
> specification, and something is better than nothing.
>
> - Steve
>
> On 21 Dec 2008, at 01:19, Nicholas J Humfrey wrote:
>
>> Reply on OSC_dev mailing list:
>>
>>
>>> #reply was first proposed in this 2004 paper by Andy W. Schmeder and
>>> Matt Wright:
>>>
>>> http://opensoundcontrol.org/publication/query-system-open-sound-
>>> control
>>>
>>
>>
>> On 20 Dec 2008, at 23:35, Nicholas J Humfrey wrote:
>>
>>> Hello,
>>>
>>> I suspect that Steve Harris may be the only person who can answer
>>> this, but I thought I would send it to the mailing list and see what
>>> others think too.
>>>
>>>
>>> There has been some discussion about replies and service discovery on
>>> the OSC devel mailing list. And I remembered that liblo already
>>> supported some of it.
>>>
>>> If you send any liblo application a message that ends with a slash
>>> (and it doesn't match any application handlers) then it will respond
>>> with a #reply message that lists the installed handlers that exist in
>>> that path level.
>>>
>>> -> /foo/bar
>>> <- #reply ssss /foo/ one two three
>>>
>>>
>>> Is this based on some kind of proposed standard? It doesn't seem to
>>> be
>>> part of "The Open Sound Control 1.0 Specification".
>>>
>>>
>>> nick.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> liblo-devel mailing list
>>> lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> liblo-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>