Bill de hOra wrote:
Brian Smith wrote:
I'm pretty sure I agree with you, but please define "stable".
Look at how twitter implements paging (it's not using atom,
but the concept stands). The content on page=2 of your
twitter changes as a function of new posts on the home page,
although the entries themselves are uniquely identified.
That's not stable.
Let's say I have this at time T:
Page: (prev)
Entry A
Entry B
Page: (current)
Entry C
Entry D
Page: (next)
Entry E
Entry F
I page through the feed and I am on the second page. Entry E gets updated before I nagivate to the next page page:
Page:
Entry E
Page: (prev)
Entry A
Entry B
Page: (current)
Entry C
Entry D
Page: (next)
Entry F
Is this still "stable"? Or does stability require snapshot semantics, like this?:
Page:
Entry E (new version)
Page: (prev)
Entry A
Entry B
Page: (current)
Entry C
Entry D
Page: (next)
Entry E (old version)
Entry F
- Brian
Call the two concepts page-stability and snapshot-stability
(snapshot-stability implies page-stability). Page-stability is a
useful concept in itself and doesn't require the overhead of snapshot
semantics. I'm most interested in page-stability personally for things
like synchronization.