Vista's 'Next Gen' TCP/IP Stack
boyko.at.netqos writes "Microsoft's new Vista TCP/IP stack might be beneficial to businesses looking to increase use of their IT infrastructure... if they did it right. Ted Romer at Network Performance Daily writes: '[Vista] now allows us to throttle outbound traffic at a client or server. For example, you can throttle the bandwidth of a particular subnet to a particular server, giving some departments more access to the servers that they need. You can even restrict outgoing bandwidth for certain peer-to-peer applications like bit torrent. This shaping can also be handy when applied to servers, allowing less bandwidth for certain users/departments, and more for others. While consumers may debate whether Vista is a worthwhile upgrade, I believe it to be important for enterprise customers who will best be able to put Vista's capabilities to their fullest potential. Of course, I'm getting it for DirectX 10 games, but that's just me.'"
because it sure reads like one
Microsoft is desperate to get business interested in their Vista product so will trot about all manner of reasons to buy it, but business are not biting, unless this Vista can make workers type faster or calc spreadsheets quicker or email faster than there is NO productivity gains unless wowing the coworker with a 3D AIGLX/Beryl like desktop counts as productive
if an Enterprise is worried about client bandwidth they would already be using a tool dedicated for the job like, say a Router
OK - it is nice, but it certainly is not new.
The network has different characteristics depending upon what point you are at on it.
... and then put a shaping router on the WAN links.
The WAN routers see the low bandwidth, higher latency serial links and such.
The servers/workstations see the high bandwidth, low latency ethernet links.
Do you really want your server(s) calculating its(their) window(s) based upon whether the request is originating across the WAN or next to it on the LAN?
This sounds like a good idea when you're talking about a single workstation, at home, connected to a cable connection or xDSL or whatever. But it sounds like soooooo many problems in the corporate environment.
Right now it is easy to find the server/workstation that is flooding the network. It's going to be very difficult when you have hundreds(thousands?) of machines that are ALL trying to maximize their bandwidth usage.
Personally, I'd prefer the ability to set the LAN parameters for the machines
If "easier to use" means "requires less knowledge", then Linux might not be "easier to use". But if "easier to use" means "consistently behaves the way a knowledgable person expects", then Linux is much "easier to use".
Censorship is telling a man he can't have a steak just because a baby can't chew it. --Mark Twain