RE: Accept-Charset support
Re overhead quantification:
A "good" browser would need to send all or most of the charsets listed
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.
>From: email@example.com [SMTP:firstname.lastname@example.org]
>Sent: Thursday, December 05, 1996 3:33 PM
>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
>>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
>Could somebody please quantify this extra overhead?