jooles, I apologize if my post came off a bit antagonistic. I come from a background of being one of four guys at Intel who developed the original Intel Network Architecture; the guy in the cubicle next to me literally wrote the Ethernet spec; I and one other guy implemented the first operating 10 megabit Ethernet; I wrote the operating system that ran the Intel Network Architecture.
I have a really, really good idea of what this stuff is capable of doing.
And I get really frustrated at how badly most of the stuff out there is implemented. I think that came through a bit in my previous post.
A couple bits of "low-hanging fruit" that could easily be addressed: 1) If they didn't design their web pages in the first place as a gazillion teeny-tiny objects that each require a separate connection to retrieve, this issue wouldn't even exist. They have complete control over that--if they consolidate their web pages into single objects, then browsers will only open a single connection. 2) Stop forking off new tasks for every connection. fork is a very expensive operation. Organize the system as server tasks that simply activate a record in a connection data structure to create a new connection.
Anyway, enough of my rant. I wish I had the time to bring a decent network operating system to market. The basic OS is actually pretty easy to do, but coming up with device drivers for all the different video controllers, network adapters, disk controllers, disk drives, printers, etc., out there is a massive undertaking. And expensive, since you have to own one of everything that exists in order to test it.
