- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 11 Jul 2014 16:13:28 -0700
- To: "K.Morgan@iaea.org" <K.Morgan@iaea.org>
- Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Nicholas Hurley <hurley@todesschaf.org>, Greg Wilkins <gregw@intalio.com>, Jeffrey Pinner <jpinner@twitter.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 11 July 2014 16:06, <K.Morgan@iaea.org> wrote: > BTW, we still work with micro-controllers with ~100K, where 16K is a significant resource commitment. In those environments, do you have to deal with arbitrary peers? Peers that might not be aware that you are so constrained? Are those micro-controllers going to be using HTTP/2 with default configuration such that they might get 100 requests immediately after accepting the connection? My point being that in environments where there is some hope of control, you can avoid the worst by convention, standard or gentlemen's agreement, not having to rely solely on what is in some RFC.
Received on Friday, 11 July 2014 23:13:57 UTC