Mark, While I'm sure the other James may have his own particular set of issues, the one pain point for me with the history spec is the use of the "previous" link to point back in time. This runs counter to the use of the previous link in both OpenSearch, APP and Gdata. It would be excellent if rather than using previous, feed history would look at the set of feeds as a list of pages ordered in reverse chronological order, where "next" pointed to the next oldest set of entries.
e.g. current=/feed.xml first=/2006/04/feed.xml next=/2006/03/feed.xml next=/2006/02/feed.xml next=/2006/01/feed.xml ... - James Mark Nottingham wrote: > > Did you find that algorithm wrong, too hard to understand/implement, or > did you just do a different take on it? Does the approach that you took > end up having the same result? > > Any suggestions on how to better document it appreciated. > > Cheers, > > > On 2006/04/26, at 8:35 PM, James Holderness wrote: > >> >> We added support for next/prev/previous links in version 0.3.0 of >> Snarfer [1]. We don't use the reconstruction algorithm suggested in >> the Feed History draft, but your example feed seems to work ok for an >> initial retrieval. There may be problems with subsequent updates, >> though, depending on how you handle items falling out the bottom of >> the main feed. >> >> Regards >> James >> >> [1] http://www.snarfware.com/ >> >> John Panzer wrote: >>> We just deployed support for [EMAIL PROTECTED]"previous" et al. for >>> AOL Journals. If anyone has a client that makes use of these >>> links, please let me know, I'd love to see if there are any >>> interoperability problems. >> >> > > > -- > Mark Nottingham http://www.mnot.net/ > >
