Re: Atom and prev links

Looks like our answer is to rename our links archive-prev/next as we intend
them to be completely readable anyways.

Thanks!

Greg

On Fri, Jun 28, 2013 at 4:19 PM, Greg Young <[email protected]> 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?
>
> Thanks,
>
> Greg
>
> On Fri, Jun 28, 2013 at 4:00 PM, Markus Lanthaler <
> [email protected]> wrote:
>
>> **
>>
>>
>> On Friday, June 28, 2013 2:10 PM, Greg Young wrote:
>>
>> > On Fri, Jun 28, 2013 at 3:04 PM, Markus Lanthaler wrote:
>> >> If I would implement a client, I wouldn't keep polling the 404.
>> >> I would just assume your feed is broken.
>> >
>> >And if I returned a 204?
>>
>> No, the status code that would make "most" sense IMO is 202.. but I would
>> still suggest to just hide the link till the resource gets created.
>>
>> --
>> Markus Lanthaler
>> @markuslanthaler
>>
>>  
>>
>
>
>
> --
> Le doute n'est pas une condition agréable, mais la certitude est absurde.
>



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