Re overhead quantification: A "good" browser would need to send all or most of the charsets listed in ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets Easy to take all the names, concatenate them and measure the size. I didn't do it but instead looked at the size of the IANA document itself which is 44282 bytes. Assuming the text contains 2/3 overhead, the accept-charset string would be 14 KB, attached to every GET. Not counting that the server would need to sort through them and find a match with a server-side available document or conversion mechanism. >-----Original Message----- >From: garym@softshore.com.au [SMTP:garym@softshore.com.au] >Sent: Thursday, December 05, 1996 3:33 PM >To: www-international@w3.org >Cc: Alan Barrett/DUB/Lotus >Subject: Re: Accept-Charset support > >On 4 Dec 96 16:00:13 EST, Alan Barrett wrote: > >>I would like to get agreement on a definite proposal of how WWW browser >>vendors >>should request a server to send UTF-8. >> >>Browser vendors are not keen to send a very long list of character sets >>accepted due to the overhead. So I propose that the browser vendors pick one >>of >>the following... >>... > >Could somebody please quantify this extra overhead? > > > >-- g. >Received on Thursday, 5 December 1996 19:53:20 UTC
This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:16 UTC