- From: Paul Leach <paulle@microsoft.com>
- Date: Wed, 3 Jul 1996 10:53:34 -0700
- To: "'yergeau@alis.ca'" <yergeau@alis.ca>, "'hardie@nasa.gov'" <hardie@nasa.gov>
- Cc: "'http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com'" <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>
Agreed 100%! This last second flap is holding up standardization and deployment of "Host:", persistent connections, and improved caching, all of which are (with only mild hyperbole) required in order that the 'net be able to continue to reliably deliver any content at all in the face of exponential growth. Nothing in 1.1 prevents accurate labelling of charset, and customer demand will either cause or not cause that to be done by content providers. I can assure you that the browsers and servers will be there to support correctly labelled content. >---------- >From: hardie@merlot.arc.nasa.gov[SMTP:hardie@merlot.arc.nasa.gov] >Subject: Re: proposed HTTP changes for charset > >[...] > >Francois, > As Harald made very clear at the meetings in Montreal, the >group proposing UTF-8 as a target for new standards recognizes the >problems associated with an installed base of clients and servers; >they made very specific exceptions in their recommendations to deal >with that situation, naming HTTP's use of IS-8859-1 as one of those >exceptions. Larry's language is appropriate for a deployed protocol >and for a reasonable transition. If you want the group to consider >tightening the language further in later revisions of HTTP 1.1, please >develop a realistic transition plan and submit it as an I.D. HTTP 1.1 >is very far along the road at this point and it is not the place to >consider a sudden, basic shift in assumed character sets. > regards, > Ted Hardie > NASA Science Internet > >
Received on Wednesday, 3 July 1996 11:32:26 UTC