[OSC_dev] Fwd: Application Profiles: oscplanet

[salsaman at xs4all.nl]

On Tue, December 23, 2008 08:09, Gaspard Bucher wrote:
> On Mon, Dec 22, 2008 at 10:41 PM,  <salsaman at xs4all.nl> wrote:
>>
>> Why would /reply_to need a . before it ? It is just a normal command,
>> its
>> not a meta-operation on other nodes.
>>
>
> Yes and no: yes, it's not a meta method, but no it's not an app
> method: it's used for communication setup and might as well live in
> the zeroconf part.
>
> I need to start implementing something that works and will use
> "/.reply_to" instead of "/reply_to" so that all commands related to
> the protocol live in "/.xxx" but this could be changed later to some
> namespace if it's better. This is a draft.
>
>> As I have pointed out several times now, this is ambiguous. Are you
>> setting /midout/channel to 4.5, or are you querying the value of
>> /midout/channel,4.5 ?
>>
>>
>
> Again, this is a limitation of libosc and we should not create a
> protocol that depends on the weirdnesses of particular
> implementations. In your case, it's obvious that you need to use what
> urls are made for: give a unique location for an object in the system:
>
> /clip/start 100 3456
>
> should be
>
> /clip/100/start 3456
>
> or
>
> /clip.100/start 3456
>
> or
>
> /clip/current/start 3456
>
> Because if the 100th clip has methods, it deserves an url. The osc
> urls are made to avoid indexing everywhere. We are doing some kind of
> exception with the meta methods that "index" on urls, but they are not
> used in a running application: they are used during setup.
>
> Gaspard


As I said, I would like to do this ! How do I create a path with variables
in it ? oscpack is out for me, since it is C++ only, so this leaves just
liblo I think.

Regards,
Gabriel.










> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>