Re: Atom and prev links
Erik Mogensen <[email protected]> Fri, 28 Jun 2013 19:06:14 +0200
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Message-ID | <CADbGZjawYAt0-9G=qiekGDUjWsTLe++9PTN63c1BarLnXj-+Zg@mail.gmail.com> |
On Fri, Jun 28, 2013 at 6:14 PM, Greg Young <[email protected]> wrote: > ** > > > We have considered this empty feed page as well! We were thinking its > slightly more efficient (and understandable) to have a status code but > maybe not (thinking client logic). > We were probably thinking that the empty page would fit nicely within an IP packet anyway, and could easily support ETag validation, and provide information about the current state "there's nothing to process now". I am curious why not a 204. It would seem to be a reasonable fit here > "keep your doc, retry after ..." > > Hmm. after reading up on RFC-2616 I'd agree with you. My understanding of 204 means that you should "stay where you were" and then I guess the client would eventually retry. RFC2616, section 10.2.5 "204 NO CONTENT" says: "If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent" — This should cause the same or a very similar outcome, I guess. I guess we should update our client to react accordingly when we encounter a 204. :-) -- -mogsie-