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
We found shared time imprecise enough, and other workarounds over HTTP
complex enough, that to solve this problem (must get all entires) we
pushed the feed out using XMPP. All the technical problems I saw then
came down to inconsistent rates of change. The simplest answer was to
get rid of HTTP and use XMPP.
cheers
Bill
