Talk:TUX web server

From Wikipedia, the free encyclopedia

Regarding the {{verify}}: TUX may support CGIs (i.e. dynamic content) now. Don't have time at the moment to look into it, but seems prudent to tag it as unverified. —Fleminra 00:44, 3 February 2006 (UTC)

Tux can run CGI's a completely separate processes. This was the original intent of CGI's, but it's also the worst possible way to run them performance-wise. Seeing as you're using TUX because it's fast, no one would consider running CGI's that way. So while it may be technically possible, it's not even close to being what you'd actually do.

However, I'll modify the article to be more specific. And I'm removing the tag. Tmassey 18:52, 5 February 2006 (UTC)

It might be worth referencing http://kerneltrap.org/node/517 when rewriting this article. For example, the NPTL work is unrelated to TUX, zerocopy and scalability are related, but aren't mentioned. zerocopy is now available to userspace httpds that want to take advantage of it. It might also be worth mentioning the AIO work, though it's not clear to me if the current TUX implementation uses the AIO implementation or whether it does its own thing -- I only skimmed the patch briefly.

[edit] Cleanup

The parts on Tux's ability to serve static and dynamic content could be better-written - it could be much clearer and more concise on what sort of content it can serve. 146.151.51.112 (talk) 12:22, 30 January 2008 (UTC)