- From: Jason Greene <jason.greene@redhat.com>
- Date: Mon, 14 Jul 2014 18:00:17 -0500
- To: Roberto Peon <grmocg@gmail.com>
- Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Patrick McManus <pmcmanus@mozilla.com>, "K.Morgan@iaea.org" <K.Morgan@iaea.org>, Martin Thomson <martin.thomson@gmail.com>, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>, David Krauss <potswa@gmail.com>
On Jul 14, 2014, at 5:09 PM, Roberto Peon <grmocg@gmail.com> wrote: > > > > On Mon, Jul 14, 2014 at 1:30 PM, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote: > In message <CAOdDvNr0PQFWm8qg7oz1tmAS3qaJK9O8fWkqoUJR9sqP+RwX1g@mail.gmail.com>, Patrick McManus > writes: > > >> I keep hearing this argument over and over. Is the goal just to finish, no > >> matter what? > > > >Of course not. But finishing is critically important. > > Absolutely, but the quality of the result is far more important > than some arbitrary deadline. > > The most important part is deployment. > This is true of transports and application-layer stuff. > .. and we know it works when folks implement things properly, because we have experience in production with real, real-world use. > The risk of getting it terribly wrong is low given this implementation experience. What about the stream dependencies though? I assume you mean the experience is the simpler SPDY priority? The spec would be a hell of a lot simpler without this dep complexity, which is what I think scares people away (well that and the scary rfc comment). -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat
Received on Monday, 14 July 2014 23:01:01 UTC