AW: Tux Patch for Linux-2.4.21-rc1

["Max Helmet" <max@expires-2004.workforce.de>]

> On Mon, 16 Jun 2003, Max Helmet wrote:
> = Nonetheless it's still one of the most advanced webservers with some key
> = advantages over thttpd, fnord and others.
                            ^^^^^
> On Thu, 2003-06-12 at 12:31, Michael T. Halligan wrote:
> You might want to consider an alternative.
> Check out fnord..
> http://www.fefe.de/fnord/

Your'e right, fnord is definetely one of the smallest and fastest webservers
and, since it's witten by Fefe, I'd bet that it's one one of the securest
too. I'd suggest its usage if a lean replacement for Apache is all what you
want. However, I want more ;-).

We're running some LAMP based community-servers and for these I'm searching
efficient ways to distribute chat-messages to many clients. AFAIK there's no
way in fnord to pipe requests that cannot be processed to Apache. So,
there's no way to run fnord and Apache on the same IP and port (aside from
load balancers etc). But that's exactly what I need, since we want to stream
JavaScript code.

We're forced to use Port 80 since other ports are likely to be blocked by
firewalls. And we're forced to use the same IP address because of the
JavaScript sandbox restrictions, which prevent us from accessing JS
functions and properties on other servers (at least, they should ;-) ). For
example, if fnord (192.168.0.2) opens a window on Apache (192.168.0.1),
afterwards, it wouldn't be able to close the window anymore. The common
solution to circumvent this problem is to separate the chat code from the
rest of the site, but we want an integrated solution, served from only one
address, with the possibility to call every function from everywhere.

Regards
Maximilian