W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1997

Re: How to add new "protocols" ?

From: Simon Spero <ses@tipper.oit.unc.edu>
Date: Tue, 18 Feb 1997 20:48:28 -0500 (EST)
To: touch@isi.edu
Cc: masinter@parc.xerox.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.SUN.3.91.970218204144.19692A-100000@tipper.oit.unc.edu>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2450
On Tue, 18 Feb 1997 touch@ISI.EDU wrote:

[ These techniques for migrating http to non backwards compatible 
protocols, which may clear up some of the other points]

> > 	1) try  alternate protocol, and use it if it works. Cache result
> > 	   of test. 
> Increases the connection latency. Bad in general. Besides, 
> which protocol do you try?

Adds an extra RTT to first connection to host

  the url format is assumed to be http://whatever/; old 
browsers need to be able to access the url when interpreting it as such; 

> > 	3) Use Upgrade: header
> Two connections are better than one?

upgrade changes the protocol to be used on the same connection
> > 	4) Use invalid method to probe. 
> Same?

same :-)

BTW, the technique I forgot was using the first part of the hostname to 
indicate a special protocol switch; failover is to fall back to http; 
there must be a suitable CNAME pointing to the right place for straight

             Now available - The Freddy Hayek Kayak
           Paddle Your Own Canoe! Be Rowed To Surfdom!
         From The Taco Institute for Dyslexic Libertarians    
Received on Tuesday, 18 February 1997 17:56:16 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:01 UTC