Re: Atom and prev links

Our whole feed is nonlossy and immutable.

On Friday, June 28, 2013, Ben Niven-Jenkins wrote:

>
>
> On 28 Jun 2013, at 11:16, Greg Young <[email protected]<javascript:;>>
> wrote:
>
> > We have a mature atom implementation for distribution of event streams
> > and as always the devil is in the details...
> >
> > The issue revolves around prev links. At some point on an atom feed
> > you will hit the current item, prev will point to the next item that
> > does not yet exist.
>
> Why not use feed paging and use prev-archive to indicate the previous page
> and keep your "main" feed as the current page.
>
> Client just polls the current page and if it needs to go further back in
> time it follows prev-archive links until it finds what it wants.
>
> You then avoid the problem of links to things that don't exist or updating
> already archived pages.
>
> Ben



-- 
Le doute n'est pas une condition agréable, mais la certitude est absurde.