Re: PEP Battle Plan [rexmit, garbled]

> Progress on an extension mechanism is essential because it is the future of
> 1.x and binary encodings of it.

I realize this is heresy here, but I have to wonder if it's worth
building the extension mechanism into HTTP.  An efficient URI
resolution protocol would allow for a smooth transition away from
HTTP 1.x and to 2.x or other protocols (smb? webnfs? multicast?), 
without invalidating old clients and without the overhead of 
establishing a TCP connection.  New protocols could then be designed 
from scratch to take into account everything that has been learned 
from HTTP, without inheriting the complexity.

It would also improve scalability, fault tolerance, ability to 
screen files (for content ratings, price, language, etc.) before 
downloading, selection of multiple variants of a resource (by 
allowing the client, rather than the server, to make the selection),  
client selection of multiple locations of a resource, etc. 

Seems like we need to take a step back and look at the web as a
whole before we commit to the direction of adding more complexity
to HTTP.


Received on Saturday, 19 October 1996 13:46:56 UTC