They seem similar. But, what if you want to have more than one paging
semantic applied to a single feed, and those uses of paging don't
align? I.e., there's contention for prev/next?
If no one shares my concern, I'll drop it... as long as I get to say
"I told you so" if/when this problem pops up :)
On 17/10/2005, at 3:21 PM, Thomas Broyer wrote:
I don't think there are different concepts of paging.
Paging is navigation through subsets (chunks) of a complete set of
entries.
If the complete set represents all the entries ever published
through an ever-changing feed document (what a feed currently is,
you subscribe with an URI and the document you get when
dereferencing the URI changes as a sliding-window upon a set of
entries), then paging allows for feed state reconstruction.
In other terms, feed state reconstruction is a facet of paging, an
application to non-incremental feeds.
I think it's worth waiting consensus on previous/next or forwards/
backwards, first/last or head/tail, etc. and having a "paging" spec
(or just IANA registration, I don't really matter), and
orthogonally define an fh:incremental extension (fh:incremental
will just change newsreaders behavior, not the paging concept).
It seems James is having the same feeling…
--
Mark Nottingham http://www.mnot.net/
