- From: David Morris <dwm@xpasc.com>
- Date: Thu, 20 Jun 2013 18:14:54 -0700 (PDT)
- cc: "'HTTP Working Group'" <ietf-http-wg@w3.org>
On Fri, 21 Jun 2013, Amos Jeffries wrote: > Which implies that server-push is a different protocol to HTTP already. Different from 1.1, but a new feature of 2.0 > IIRC: the 64K limit is for next-generation requirements of systems running > HTTP at TB speeds. Allowing new frames to be added for those larger line rates > is very useful given they are already on the horizon and HTTP/2.0 has long > lifetime ahead. In the SF Interim, we agreed to 64K/16K (frame/vs HTTP) to allow for the larger frame required to establish a TLS connection without added round trips because the initial TLS setup exceeded a single frame.
Received on Friday, 21 June 2013 01:15:23 UTC