occi-wg

Download

occi-wg@lists.ogf.org

March 2012

14 participants
22 discussions

Unsubscribe
by Ian Osborne 02 Mar '12

02 Mar '12

Please. Ian Osborne Intellect Skype: ianfos M: +44 (0) 7793 258219 T: +44 (0) 20 7331 2054 ian.osborne(a)intellectuk.org www.intellectuk.org -----Original Message----- From: occi-wg-bounces(a)ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of occi-wg-request(a)ogf.org Sent: 01 March 2012 17:00 To: occi-wg(a)ogf.org Subject: occi-wg Digest, Vol 36, Issue 2 Send occi-wg mailing list submissions to occi-wg(a)ogf.org To subscribe or unsubscribe via the World Wide Web, visit https://www.ogf.org/mailman/listinfo/occi-wg or, via email, send a message with subject or body 'help' to occi-wg-request(a)ogf.org You can reach the person managing the list at occi-wg-owner(a)ogf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of occi-wg digest..." Today's Topics: 1. Re: JSON Rendering proposal, rev 2 (alexander.papaspyrou(a)tu-dortmund.de) ---------------------------------------------------------------------- Message: 1 Date: Thu, 1 Mar 2012 13:59:16 +0000 From: <alexander.papaspyrou(a)tu-dortmund.de> To: <ralf(a)nyren.net> Cc: occi-wg(a)ogf.org Subject: Re: [occi-wg] JSON Rendering proposal, rev 2 Message-ID: <EF2ABD5F-836A-49CC-A18C-F6E8A3BC3DAE(a)tu-dortmund.de> Content-Type: text/plain; charset="us-ascii" Am 01.03.2012 um 12:44 schrieb Ralf Nyren: > On Wed, 29 Feb 2012 14:36:16 -0700, Gary Mazz > <garymazzaferro(a)gmail.com> > wrote: > > Good point, thanks for taking time to explain. We simply leave it up > to the client to maintain state on which "page" it has requested last. > Protocol-wise paging only exist on the query level then. > > I would like to leave the "total collection size" value in the data > format though. That way a server still has the option to throttle the > response size when necessary. > > Something like this then? > > "Get 50-entries page _after_ resource xxx": > GET /compute/?marker=xxx&start=1&end=51 > > "Get 50-entries page _before_ resource xxx": > GET /compute/?marker=xxx&start=-1&end=-51 > > "Get 10 resources _including_ resource xxx": > GET / compute/?marker=xxx&start=0&end=10 More or less. We have to check inhowfar this needs to be done as parts of the query paramaters, and how this can be sensibly combined with RFC5988 information. -A. -- Alexander Papaspyrou alexander.papaspyrou(a)tu-dortmund.de

1 0

JSON Rendering proposal, rev 2
by Ralf Nyren 01 Mar '12

01 Mar '12

Hi all, I finally got some time to work on the JSON Rendering. The document now include a formal description of the JSON formats, almost complete (I hope). I have tried to incorporate much of the feedback received so far. Short summary: - Use separate media-types for rendering the different payload contents. Inspired from Florians references to the CDMI spec. - Try to make the single-instance format more lightweight and not duplicating any information available through the discovery interface. Thanks Jamie. - Use the "marker" concept from OpenStack for pagination as suggested by Andy. - "range" and "default" attribute properties as requested by Florian. PDF attached and latex sources committed to gridforge. Comments welcome. Unfortunately I will not be able to attend the plugfest but if you plan a session on discussing the JSON rendering please let me know and I'll call in. regards, Ralf

4 12