Correct me if I'm wrong but currently we send Accepts in a single outward
call and get some form of result (either the document or an error)
returned from the server. With your scheme we send a request, receive a
list of possible types, send back a request for types the client can
handle and then get the reponse from the server. Therefore we've gone
from one round trip delay to two. Thus to save transmitting a few bytes
we take an increased latency hit. Right? When some of the network links
have RTDs in the thousands of ms from where I'm sitting and yet we have a
nice fat pipe to the Internet, I think we'd rather waste a few bytes on
small documents. Latency is Your Enemy(tm) in WAN based distributed systems.
Just IMHO.
Jon
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon Knight, Research Student in High Performance Networking and Distributed
Systems in the Department of _Computer_Studies_ at Loughborough University.
* Its not how big your share is, its how much you share that's important. *