[OSC_dev] Fwd: Application Profiles: oscplanet

[salsaman at xs4all.nl]

On Mon, December 22, 2008 20:23, Jamie Bullock wrote:
> Hi Gaspard,
>
> On Mon, 2008-12-22 at 16:39 +0100, Gaspard Bucher wrote:
>> On Mon, Dec 22, 2008 at 10:22 AM, Jamie Bullock <jamie at postlude.co.uk>
> wrote:
>> > /info /foo/bar
>> >
>> > This has the advantage of being super-easy to parse on the server,
> and
>> > has the nice effect that you get a top-level 'meta' address space
>> > (/info, /reply_to etc.) before you have added any
> 'application-specific'
>> > methods. More details in this post:  http://tr.im/2jl4
>> Fine ! I want my parser to be fast and putting all meta in special
>> urls makes it faster and cleaner. In rubyk, most of the objects live
>> at the root "/". Could we move all meta methods in something like
>> "/osc" or "/meta" or "/~" or "/:" ? If we do not do this, I will have
>> to move the nodes and since node methods are called 1000x more often
>> then meta methods (only used during setup), I think they should get
>> shorter urls. If you don't mind that we use some kind of prefix,
>> either as a container or just on the methods themselves, I think "/."
>> is simple and easy.
>
> I think that's a great idea!
>
>> Many projects have some meta content at the root
>> contained in a ".xxx" (.git, .profile, .ssh, etc) so this should be
>> quite natural.
>>
>> /.info /some/url
>> /.reply_to
>
> Yes, I like this a lot. I'd certainly be willing to adopt it in Integra.
> It makes intuitive sense to me coming from years of *n*x ;)
>
>>
>> > <snip>
>>
>> >> a. /reply_to
>> > Agree!
>>
>> Becomes /.reply_to
> Yup.
>
>
>>
>> I think it's a good idea to forget about meta things in special
>> syntaxes (makes the processor slow), even for tiny things such as
>> trailing "/". Let's go for:
>>
>> /.list /some/url
>>
>> Or even
>>
>> /.ls /some/url
>
> Hm, I wonder if we can have both, with '/.ls' being an alias for
> '/.list'?
>

Please can we use something other than .list for this - I would like to
reserve .list for listing instances of things, for example:

/.list /video/effect  -> return a list of names of video effects.


Instead I suggest /.nodelist to return the list of nodes at a particular
level.



Gabriel.