On 15/10/05 12:48 AM, "Mark Nottingham" <[EMAIL PROTECTED]> wrote:
> Also -- I'd think that the "last" link is already covered by "self,"
> no? If not, there's some pretty serious confusion about what 'self'
> means.
What if a magazine publishes articles only once per month, each month's
entries are all in one feed document, each feed document with unique URIs,
and the public 'self' URI simply redirects to the last feed document.
That is:
http://example.com/monthly/current.atom
redirects to
http://example.com/monthly/2005-10.atom
Of course you can find the 'last' archive via the 'self' URI, but that
doesn't make them the same thing. If you were paging through using 'next',
how would you know you've reached the 'last' ... apart from running out of
'next' links, and apart from separately retrieving the 'self' URI and noting
the eventual URI handed back so you can compare against the one in 'last'.
Why would anyone want to know the 'last' link? One use case is that one
could take note of the 'last' URI, and then later find out what the 'last'
URI now is ... and if they are different then obviously more has been added
and it's time to go fetch.
e.
