3 ms·
While it would be exciting to see something as progressive as SPDY become codified as a standard, keep in mind the deliberately conservative nature of standards
by kibwen 15y ago
While it would be exciting to see something as progressive as SPDY become codified as a standard, keep in mind the deliberately conservative nature of standards development, as seen in the responses to that message:
On 24/01/2012, at 3:50 PM, James Snell wrote:
> +1... would love to see that work move forward within this group. I do
> have concerns about keeping the scope focused, however. Even tho the
> door would be opened to the possibility of new features being
> introduced, there is obvious danger in opening those doors too wide. I
> strongly feel that things such as the introduction of new request
> methods and new header fields, unless there is clear and irrefutable
> evidence of their general utility within the core of the spec, should
> continue to be pursued as they are today -- within separate I-D's as
> extensions to the core protocol. The charter should make it absolutely
> clear that the goal is an incremental evolution of HTTP/1.1 rather
> than an opportunity for radical changes.
Thanks, James.
Pretty much everyone I've spoken to about this has raised the same concern.
I agree it's going to be a tightrope walk, but I think there's a healthy
amount of concern about this in the community, which will help guide development.
Cheers,
Mark Nottingham