[OSC_dev] Application Profiles

[salsaman at xs4all.nl]

On Sun, December 21, 2008 14:05, Nicholas J Humfrey wrote:
>
> On 21 Dec 2008, at 11:54, salsaman at xs4all.nl wrote:
>
>> On Sun, December 21, 2008 10:47, Gaspard Bucher wrote:
>>
>>> 4. Node listing
>>> /some/path/
>>>
>>> Ending "/" = listing.
>>>
>>
>> This is not allowed for reasons which I have already explained (libOSC
>> does not allow methods containing "/")
>>
>> Instead we have /node(leaves) or /node#leaves if that is preferred.
>
>
> Isn't the method name effectively empty, rather than containing a '/' ?
>
> That seems like a limitation of libOSC rather than the OSC itself. Is
> it not fixable?
>
>
> nick.


I don't know if its fixable, but currently the way libOSC works:

you add various containers, eg.

/foo
/bar

each container can have associated methods, e.g.

/foo/aaa
/foo/bbb


Now I try to add a method "aaa/#info" to container /foo and libOSC will
not allow me to, since "/" is not allowed in a method name.

The solution would be to add each method as a container as well, but it
would be quite a lot of effort to do this.

So I prefer to add methods like: aaa(info), aaa(leaves) which do not cause
problems.


However, there is some code in libOSC which does something when a message
ends in a "/". I am not exactly sure what it does, I think it returns part
of the tree, but I would rather have the control to filter what exactly is
returned.



Gabriel.