[
https://issues.apache.org/jira/browse/OLINGO-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072311#comment-15072311
]
Ramesh Reddy commented on OLINGO-838:
-------------------------------------
[~pratyush.,iitg] If you are implementing server side paging you need to make
use of $skiptoken, there if you got some kind of session based cache on server,
you can use session identifier as part of the skiptoken to implement state.
> How server side pagination is supported for ODATA in Olingo?
> ------------------------------------------------------------
>
> Key: OLINGO-838
> URL: https://issues.apache.org/jira/browse/OLINGO-838
> Project: Olingo
> Issue Type: Question
> Components: odata2-core
> Affects Versions: V2 2.0.3
> Reporter: Kumar Pratyush
> Priority: Critical
> Labels: ODATA, pagination, server-side
>
> Hi,
> How server side pagination is implemented for ODATA?
> Let's say we have around 10GB of data. So we will get the data in different
> pages and we will be getting next link for remaining data. But if some other
> user inserts or deletes data in parallel, then how will it ensure the
> consistency of data?
> Expected result will get changed or server will do some kind of cashing or
> save the state of client? As ODATA is based on rest principles, so server
> should not save the state of client.
> Thanks and Regards,
> Pratyush
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
