I'll try to pursue both of Tony's suggestions this weekend in Mosaic.
If neither solves the problem completely, I suggest as the easiest
solution that we require that existing HTTP0 servers *at least* be
upgraded to be able to accept full, multiline HTTP/1.0 queries, even
if they can't understand them.
If backward compatibility for HTTP0 servers is essential and such a
required partial upgrade situation wouldn't be acceptable, I then
suggest that browsers begin supporting a "http0:" URL type for the
sole purpose of communicating with old servers.
I make these specific suggestions because I think that changing either
HTTP0 or HTTP/1.0 at this point would be much more painful -- HTTP0
has served us well and is ideal for what it is (very simple, very
lightweight, and very easy to build shell scripts around -- my
proposed partial upgrade situation described above should leave those
qualities intact), and HTTP/1.0 is already achieving critical mass (by
virtue of Plexus and CERN httpd 2.x) and clients are already either
supporting it or will very soon.
I know Eric already disagrees with me already, and I'm sure others
will too, and I'm flexible on this -- *however*, I think we need to
value cohesion and stability more than almost any other factor at this
point, particularly as we are in the midst of a successful move to