[OASIS Issue Tracker] Updated: (ODATA-399) Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/ODATA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-399:
-----------------------------

    Environment: [Applied]  (was: [Proposed])
       Assignee: Ralf Handl

> Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging
> ------------------------------------------------------------------------------------------
>
>                 Key: ODATA-399
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-399
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_CSD01
>         Environment: [Applied]
>            Reporter: Stefan Drees
>            Assignee: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> We should say something about what to expect when a next-link expires (as we are storage model agnostic and cannot assume, that this 
> will always be a reconstructable query).
> This might apply to other opaque tokens that act as URLs to retrievable resources.
> As of now we do not describe this in any detail.
> A common scenario from the interactive browsing would be a client stepping through a paged result set and "bookmarking" a certain page for later retrieval. This might be due to relevance of the pages content or as a planned re-entrance point for resuming some analysis of the result set (both motivations assuming the result set is somewhat constant or only  slowly changing).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira