+1 (with the non-committer hat in mind ;-)
I find the /foo.all.json and /foo.1.json notation very intuitive. And /
foo.json only returns the foo node and its properties.
Alex
Am 09.01.2008 um 16:58 schrieb [EMAIL PROTECTED]:
I like felix's idea of using selectors. I would hate to call /
foo.json and get it and all its child nodes. Think of a file system,
you don't expect to request the root folder and get a full dump.
However, if you requested /foo.recurs.json you may expect a full dump.
Paddy
Sent via BlackBerry from T-Mobile
-----Original Message-----
From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
Date: Wed, 9 Jan 2008 16:41:20
To:[email protected]
Subject: Re: json export: recursive by default
On Jan 9, 2008 4:08 PM, Tobias Bocanegra <[EMAIL PROTECTED]>
wrote:
Isn't that a bit dangerous?
A json GET at / would then get the whole repository...
and how would you do that? is there a way addressing the root node ?
GET /.json HTTP/1.1 ?
Ok, not the root then, but GET /content.json will still dump the whole
/content subtree if full recursion is the default.
-Bertrand
--
Alexander Klimetschek
[EMAIL PROTECTED]
