On Thu, 2007-02-15 at 12:32 +0100, Rhythmic Fistman wrote: > Not quite - the c10k problem is to do with serving thousands of clients, > i.e. disk->network traffic. felix's considerable contribution to this has been > the complete removal of the scheduler consideration*, pushing the > issue back to the OS's > socket/disk IO implementation and related readiness interfaces**.
That's right. And that is why we probably need to use a single raw socket on port 80, and re-implement the required part of the TCP/IP protocol on top of that: potential commercial project for Async P/L. -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Felix-language mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/felix-language
