OK, but that still leaves us with the question below -- who's doing
the paging, and why is it useful to have multiple ways around the thing?
On 15/10/2005, at 7:25 PM, Eric Scheid wrote:
On 16/10/05 6:54 AM, "Mark Nottingham" <[EMAIL PROTECTED]> wrote:
Can you walk me through a use case where this would be desirable?
E.g. what would the subscription URI be, would any of the entries
be updated, and how if so? In what scenario would having a closed
set feed be useful?
An archive for a blog that is no longer being updated? An archive
of entries pertaining to an event with a fixed endpoint? A
discussion forum that has been closed.
How are implementations supposed to use this information? Stop
polling the feed? Consider its items immutable? I'm concerned if
something so innocent-looking as "last" has these sorts of
implications.
perhaps a better example would then be a feed of search results,
which at
any time of query is a finite and closed set, and also designed to
be paged
through.
e.
--
Mark Nottingham Principal Technologist
Office of the CTO BEA Systems
