RE: Atom and prev links

On Friday, June 28, 2013 3:19 PM, Greg Young wrote
> btw in doing some research it would appear that RFC 5005 allows
> for either in the areas where reading of feeds is actually discussed.
> 
> This process
>   should be repeated recursively until the client encounters a prev-
>   archive link relation that has been processed (the end of the archive
>   is indicated by a missing prev-archive link relation) or an error is
>   encountered.
>
> prev/next reading is not discussed but would seem logical to work in the
> same way. I am unsure why it would be "broken" as you say to return an
> error. Can link me to the relevant specification?

I didn't say that a spec prohibits it, how could it? You have to expect
broken links everywhere. I just said I would assume that your implementation
is broken because it creates links that lead to a 404.

Errors shouldn't control the *normal* control flow, they should be
exceptions.



--
Markus Lanthaler
@markuslanthaler