Re: [hybi] Framing proposal with start/end demarcation

James Graham <jgraham@opera.com> Thu, 05 August 2010 20:11 UTC

Return-Path: <jgraham@opera.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D8C23A693F for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 13:11:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.481
X-Spam-Level:
X-Spam-Status: No, score=-6.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N87Rmde-PnRi for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 13:11:34 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by core3.amsl.com (Postfix) with ESMTP id 99EDF3A6936 for <hybi@ietf.org>; Thu, 5 Aug 2010 13:11:33 -0700 (PDT)
Received: from sirius.linkoping.osa (sgw-oslo2.opera.com [213.236.208.46]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id o75KBvO4023397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 5 Aug 2010 20:11:58 GMT
Date: Thu, 05 Aug 2010 22:11:56 +0200
From: James Graham <jgraham@opera.com>
X-X-Sender: james@sirius
To: Roberto Peon <fenix@google.com>
In-Reply-To: <AANLkTinqaN5p8OHgrLA-cgHPP7ONBW7uGVnjJ_B1B8hD@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1008052155060.12845@sirius>
References: <4C5651AB.2020005@mail-abuse.org> <AANLkTikaruGt6pXacHWqF+FAkgXg1uh3kN4RPyay+bnR@mail.gmail.com> <Pine.LNX.4.64.1008040808390.5947@ps20323.dreamhostps.com> <AANLkTik+mEKsZz8-CojnMip1Vpp06f6uutNX3eT6gPpD@mail.gmail.com> <Pine.LNX.4.64.1008041803400.5947@ps20323.dreamhostps.com> <AANLkTinQtkGLf+YvJ5c724nas3xqbRchfHSRkfKoEb5u@mail.gmail.com> <op.vgyd890464w2qv@anne-van-kesterens-macbook-pro.local> <AANLkTin9wTTzrLNSu5AZz+MLx4NT-PHZV0kj8tv4RKm+@mail.gmail.com> <op.vgykq4ul64w2qv@anne-van-kesterens-macbook-pro.local> <AANLkTik4bcOFkdvq3DWuDs1RRLPzXCEyvHK1ef1dAr8E@mail.gmail.com> <4C5AD3F6.90108@opera.com> <AANLkTim+tsT8jh=s0mUKvkVSQceG7kPxhg7J-0_yCKmH@mail.gmail.com> <4C5AE0CA.9050007@opera.com> <AANLkTimZdxYuO8usffaSKVNpG97dDbm5uTT2yhyJa2pP@mail.gmail.com> <4C5AEF4A.3020103@opera.com> <AANLkTinM90MVG0fxN0q3xJc1a54FPWzU6bvvr3gPB8uQ@mail.gmail.com> <alpine.DEB.2.00.1008051939230.12845@sirius> <AANLkTinqaN5p8OHgrLA-cgHPP7ONBW7uGVnjJ_B1B8hD@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-278719071-1281039118=:12845"
Cc: hybi@ietf.org
Subject: Re: [hybi] Framing proposal with start/end demarcation
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Aug 2010 20:11:35 -0000


On Thu, 5 Aug 2010, Roberto Peon wrote:


> What is the incentive for Mozilla, Opera, and Safari to change their implementations again in the future? When will this happen? 

Competition. If some website works better in a competitor due to some 
extra functionality, there exists a strong incentive for everyone else to 
implement that feature. The result of this is that the modern web platform 
has been stiched together from a patchwork of mutually reverse-engineered 
bugs and features. Occasionally there has even been a standards body 
involved somewhere along the way. Indeed that appears to be increasingly 
common, much to everyone's relief.

Of couse the same force that drives forward progress stops us changing the 
past; we can't take out features that are needed for existing websites to 
work even if they would have great payback over the long term. So changes 
we make to the protocol in the future have to be backwards compatible.