Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on TCP Fast Open: expediting web services. Parent comment
> 9.1.2 Idempotent Methods
> The methods GET, HEAD,
> PUT and DELETE share this property. Also, the methods OPTIONS and
> TRACE SHOULD NOT have side effects, and so are inherently idempotent.
RFC 2119
> 4. SHOULD NOT
> This phrase, or the phrase "NOT RECOMMENDED" mean that
> there may exist valid reasons in particular circumstances when the
> particular behavior is acceptable or even useful, but the full
> implications should be understood and the case carefully weighed
> before implementing any behavior described with this label.
What could possibly go wrong?
Obviously we aren't going to be able to blindly enable this optimisation without making sure our apps meet the assumptions first.
There are no comments on this comment yet.
> 9.1.2 Idempotent Methods
> The methods GET, HEAD,
> PUT and DELETE share this property. Also, the methods OPTIONS and
> TRACE SHOULD NOT have side effects, and so are inherently idempotent.
RFC 2119
> 4. SHOULD NOT
> This phrase, or the phrase "NOT RECOMMENDED" mean that
> there may exist valid reasons in particular circumstances when the
> particular behavior is acceptable or even useful, but the full
> implications should be understood and the case carefully weighed
> before implementing any behavior described with this label.
What could possibly go wrong?
Obviously we aren't going to be able to blindly enable this optimisation without making sure our apps meet the assumptions first.