Open Stack

On 25/10/2011, at 4:59 PM, Mark McLoughlin wrote:

> Why are servers different images and users here? Is that just a typo and
> you left out the "{server_id}"?
> 
> Thing is, I prefer it - IMHO, the catalogue should list collections and
> individual items in the collection can be retrieved by querying the
> collection. If a client has a entity ID, it should be able to use query
> parameters to efficiently obtain it and then it can retain the URI for
> future use.
> 
> I'm not so keen on requiring clients interpret URI templates in order to
> navigate the top-level catalogue. There just isn't a lot of client
> support out there. And while the above templates are straightforward,
> once you say that a link target is a URI template the client must
> support all aspects of the template syntax.

I think there's a discussion to be had there. 

URI templates haven't seen wide deployment yet because the draft has been dormant for so long (sorry), but Roy's put a fair amount of work into it recently, and is making noises about shipping it soon. I'm also hearing about multiple implementations (even in C) based on the recent work. 

I'm wary of assigning resources the magical name "collection" with the implication that you can assume very specific behaviours regarding query parameter parsing, etc.; it's very tightly coupled. 

Cheers,

--
Mark Nottingham   http://www.mnot.net/