Eric Scheid wrote:
I've been amusing myself with a thought experiment this morning too. Say I
had a set of feed documents, all arranged from "hottest" to "coldest"
using
@rel='hotter' and @rel='colder'. There are no other links in the feed
documents. Say for the sake of argument that the most efficient manner for
an aggregator to traverse that set is to start from the hottest, and
proceed
towards the coldest.
Remember, there are only two @rel values in the feed: 'hotter' and
'colder'.
Which links should the aggregator follow:
In the interests of past and future compatibility, my currently
implementation looks like this:
1. In the subscription document, look for a link with a type of
"application/atom+xml", a non-empty href, and with any of the following rel
values: "next", "prev", "prev-archive", "hotter", "colder".
2. If any such link exists, consider it a pointer to the most recent
archive.
3. To find the next most recent archive, search the current archive for a
link with the same rel attribute as established in step 1.
Can't fail. ;)
In the interests of my sanity, I'm bowing out of this discussion now.
Whatever is decided I will implement it.
Regards
James