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

Re: How to add new "protocols" ?

From: <touch@isi.edu>
Date: Tue, 18 Feb 1997 18:23:12 -0800
Message-Id: <199702190223.AA04284@ash-s.isi.edu>
To: touch@isi.edu, ses@tipper.oit.unc.edu
Cc: masinter@parc.xerox.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
> From ses@tipper.oit.unc.edu Tue Feb 18 17:48:32 1997
> 
> 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
> > Increases the connection latency. Bad in general. Besides, 
> 
> Adds an extra RTT to first connection to host

Only if "fails" is by NACK. Otherwise, it adds
a timeout, which is usually in the 2-3*RTT range, _at best_.

> > > 	3) Use Upgrade: header
> > Two connections are better than one?
> 
> upgrade changes the protocol to be used on the same connection

We were talking about alternate transport protocols, not application
protocols. How does one change the transport protocol without
opening another connection?

> 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
> http.

What is the 'first part of the hostname'? ARe you parsing
DNS names and redefining parts thereof??

Joe
----------------------------------------------------------------------
Joe Touch - touch@isi.edu		    http://www.isi.edu/~touch/
ISI / Project Leader, ATOMIC-2, LSAM       http://www.isi.edu/atomic2/
USC / Research Assistant Prof.                http://www.isi.edu/lsam/
Received on Tuesday, 18 February 1997 18:29:05 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:29 EDT