RE: HTTP version 1.0 or 1.1?

I like it -- it would be nice to have a good spec for what to do to 
interoperate with the current deployed browsers/servers (warts and all...).

I'd have second thoughts if you said it would take a long time, but if 
it can really be accomplished in a few days, and you're willing to do 
the work, I'd concur.
----------
] From: Roy Fielding  <fielding@beach.w3.org>
] To:  <netmail!http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>
] Subject: HTTP version 1.0 or 1.1?
] Date: Friday, August 11, 1995 11:46AM
]
] I have had several comments sent to me (most off the list) along the
] lines of "how can we keep changing 1.0 when there are deployed apps?"
] and "how can I know whether a server supports the standard or not if
] we continue to use the same version number?", etc.
]
] As we mentioned back in San Jose, we have a choice as to whether
] we try to standardize 1.0, or release a current-practice document on
] 1.0 and move our standard to HTTP/1.1 (which in turn would mean that
] what we are currently calling 1.1 features would be in HTTP/1.2).
]
] Since the IETF recently created the BCP ("Best Current Practice")
] series, we can actually do this now within a reasonable framework.
]
] The action required would be for Henrik and I to create a stripped-down
] HTTP/1.0 document and release it along with the current draft renamed
] as HTTP/1.1.  This will take three days for us to accomplish, but may
] be worth the saving in confusion and aggravation.
]
] Does the WG want to do this?
]
]
]  ....Roy T. Fielding  Department of ICS, University of California, Irvine USA
]                       Visiting Scholar, MIT/LCS + World-Wide Web Consortium
]                       (fielding@w3.org)                (fielding@ics.uci.edu)
]

Received on Friday, 11 August 1995 12:20:56 UTC