More on Paging

As you can imagine, several Oracle products are struggling with paging.
I had a chat with a couple of those folks and they had some interesting insights
based on several interfaces they have studied.

1.  Next/Prev URIs are not necessary.  The client can just send a sendNext or sendPrev
command and the server can decide what to send.  Or, the client can request a range
of items based on a URI template.

2. On closer examination, snapshots are more expensive than I had originally thought.
If the client really, really wants consistency we can provide commands to create a snapshot
and then page from that snapshot.

3. A better alternative is for the server to cache the collection and then page from that
cache.    Clearly, not an option for huge collections.

4. It is quite difficult to create eTags for the collection to check if it has been modified while
paging thru it.    We discussed various database techniques that may help such as System
Commit Number but none seemed to offer a good solution.

All the best, Ashok

Received on Saturday, 3 May 2014 14:02:53 UTC