The best solution is just to add a link types to the atom syntax: a
link to the previous feed document that points to the next bunch of
entries. IE. do what web sites do. If you can't find your answer on
the first page, go look at the next page.
How do you know when to stop? If the pages are ordered
chronologically, the client will know to stop
when he has come to a page with entries with update times before the
date he last looked.
This is:
- simple,
- easy to see (no need to look at invisible header fields),
- easy to understand (no need to read another complicated rfc
document)
- easy to implement (well it so simple)
- low tech (you don't need anything more than a server
supporting http)
Henry
On 17 Jun 2005, at 00:37, James M Snell wrote:
Ok, question for the group.
Scenario: A content source is updated 100 times per hour. The Atom
feed currently only displays the 20 most recent entries. Users who
are not checking the feed every 10 minutes or so are missing
entries. How do we address this?
Solution: Rather than using a feed with a fixed number of entries,
provide a mechanism that allows users to specify the last time they
retrieved the feed and have the feed return all entries added since
that time.
Question: What is the best way to provide that mechanism:
querystring parameter or HTTP header or some other way I'm not
thinking of
http://...?last-retrieved=12345
OR
GET ... HTTP/1.1
Host: ...
Last-Retrieved: 12345
- James
