GeekForce

Leo Laporte twittered that ‘Text is so tiny - what an efficient medium’.
You know, the internet still has throwbacks to the 7bit ASCII days. the FTP protocol only support UTF-8 as of 2002, and who knows how many servers actually implement that?

ftp://ftp.ietf.org/internet-drafts/draft-ietf-ftpext-utf-8-option-00.txt

I did some research and found the above link. it’s been awhile since i asked this question, the last time was about 15 years ago, when I asked the Network Administrator at MVP-Net when the 7bit ascii was going to be phased out in favor of 8bit. It always seemed like this would be more efficient use of the bits that we had to spare…

So, these days, I know that the content-eoncoding is dealt with by the server, and the client reads that information from the HTTP headers.
That’s all fine and good, but is there a provision for the HTTP commands to arrive with such encodings?
Thats a question I cont answer right now. My guess is ‘NO’ because then PUT wouldnt necessarily be PUT, would it? Oh it’d be 3 glyphs? (nope, that’s for typography)… It’d be 3 characters wirth of data, but it might not be the right 3…
Anyhoo, I dont know about this… But I wanted to point out that text is very compact, but it does lack any presentation information…