Re: [dev] Re: Why HTTP is so bad?

From: Andrew Gwozdziewycz <web_AT_apgwoz.com>
Date: Wed, 22 May 2013 16:43:15 -0400

On Wed, May 22, 2013 at 4:24 PM, Thorsten Glaser <tg_AT_mirbsd.de> wrote:

> Andrew Gwozdziewycz dixit:
>
> >Not really, given that HTML has *nothing* to do with HTTP.
>
> Both are overused, really.
>

You won't find me arguing against this statement.

>Of course, you often retrieve HTML documents via HTTP
>
> Doing anything else (well, file download is also okay),
> such as this XMLRPC crap, or even tunneling, over HTTP
> instead of just using plain TCP is probably the thing
> the original poster disagreed with. Me too, btw… it’s
> an illness of the age of the “webdesigner” ☹
>

It's really not just the "illness" of the webdesigner. It's more the
illness of the industry. Keep in mind that we're quickly moving to the
cloud, and building devices that have little more than a web browser as an
interface to it. Web browsers typically speak HTTP best, and at best,
sometimes allow for other layer 7 protocols to be utilized (FTP, perhaps
gopher).

Though, to be fair, Chrome does (or is going to) support actual TCP sockets
for extensions.
Received on Wed May 22 2013 - 22:43:15 CEST