W3C home > Mailing lists > Public > public-ldp-wg@w3.org > September 2013

Re: Client initiated vs Service initiated paging

From: Arnaud Le Hors <lehors@us.ibm.com>
Date: Fri, 20 Sep 2013 18:25:11 -0700
To: Steve K Speicher <sspeiche@us.ibm.com>, John Arwe <johnarwe@us.ibm.com>, "ashok malhotra" <ashok.malhotra@oracle.com>
Cc: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Message-ID: <OF704839B7.C113B5E4-ON88257BED.0006B036-88257BED.0007CC17@us.ibm.com>
I haven't seen any response from the editors and from what I can tell the 
first comment hasn't been taken care of. I think Nandana is right though, 
isn't he?
Arnaud  Le Hors - Software Standards Architect - IBM Software Group

From:   Nandana Mihindukulasooriya <nmihindu@fi.upm.es>
To:     "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>, 
Date:   09/10/2013 07:16 PM
Subject:        Client initiated vs Service initiated paging


As the LDP spec stands now all the paging will be server initiated i.e. a 
client doesn't have a say whether a resource will be paged or not, isn't 
it ? So may be the term client-initiated paging could be a bit 

[[ LDPR servers must indicate their support for client-initiated 
paging by responding to a HTTP OPTIONS request on the LDPR’s URL with the 
HTTP response header for link relations using the header name of Link and 
link relation type first [RFC5988].

Also in the following section, something seems to be missing when the spec 
says 'See for additional details.'.

[[ LDPR servers may split the response representation of any LDPR. 
This is known as server-initiated paging. See for additional details.

Best regards,

Received on Saturday, 21 September 2013 01:25:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:44 UTC