Extended Uses of Tux

Hello Ingo et al.,

thank you for this fine piece of code, we all appreciate your continuous
efforts to make it even better. Personally I feel really relieved to see Tux
revived as it is more than "just" an extremely efficient HTTP server to me.
Its unique feature to forward HTTP requests that it can't handle to a
backend server makes it an ideal solution for an "integrated chat server".

What I mean with it is a system that delivers web pages and HTTP chat
streams from the same IP, the same host and the same port. Up to now you
have to outhouse the chat part of a website to a different host, a strategy
that imposes some problems with JavaScript (sandbox restrictions), cookies
(differences between subdomain cookies on country level domains and
com/net/org), multiple SSL certificates, the need for cross site image
references and so on.

I wrote these lines to make you aware of these extended areas of application
in order to motivate you and your colleagues to keep faith with Tux even if
it hasn't found its way into the official kernel yet (actually, I doubt it
will ever). And maybe someday your marketing folks think over their
mistakable branding of Tux as just a "content accellerator"... ;-)

Thanks again and best regards,
Max