“Microsoft still is expected to deliver the next Windows Vista milestone, the February Community Technology Preview release, next week – most likely on Feb. 21, according to testers briefed last month by Microsoft.” In addition, “the company has begun testing a Quality of Service feature, which will be in both Vista and Longhorn Server. QoS technology helps cut down network congestion while optimizing traffic to the available bandwidth. QoS becomes useful when customers have multimedia applications or Voice over IP.”
I’m pretty sure QoS is already in WinXP/Win2k3…is there something different and/or new about the QoS in Vista/Longhorn Server?
Yes, of course. WinXP has QoS service when you look in the service manager.
I just hope they won’t say it is “innovative” technology.
Na, I’d say it’ll be more fine tuning of the existing technology – I also understand they’ve given their TCP/IP stack an overhaul as well, so it’ll be interesting to see how it performs in terms of server stress testing.
Qos isn’t anything innovative, it’s been in the various BSD’s and Linux for ages and ages. I am looking forward to seeing how the “new tcp/ip stack” performs vs previous incarnations.
…Microsoft in the news with nothing of any value to announce or offer… when you have unlimited money and a team of PR agents, it isn’t hard.
Not much about their dilemma with the EC, though…
Substitute Microsoft for Linux and you’ll have it right.
I would say the only dilemma here is the Linux community trying to handle the Microsoft jagernaut. MS keeps piling on the features, improving security and reliability and linux just continues to struggle to keep up (just like the last 10 years).
No amount of anti-MS FUD will that the situation. You guys (OSS community) need to innovate and come up with your own ideas. Stop copying the Windows interface (KDE cheap rip-off), stop using windows drivers for wireless networking, etc…
Go invent your own ideas for once…
I love you for that comment. Seriously it’s like you read my mind.
You know judging by your:
1. nickname
2. attitude
3. various posts on various topics on OSNews
You sir, are a troll and a bad one at that. Your posts are off topic, your attitude is self-righteous my-enemies are dumb and your lies are stupud. I will not even waste my time to argument over the crap you managed to get out of yourself here.
On topic: Currently windows TCP/IP stack and the whole winapi just sucks. As a network lib developer I can plainly say so, compared to BSDs for example windows is some 10 years behind. On the other hand they do have some multi-threading potential which might come in handy with heavy multicore cpus of the future. The QoS thing is imho just a marketing hype thing.
Currently windows TCP/IP stack and the whole winapi just sucks. As a network lib developer I can plainly say so, compared to BSDs for example windows is some 10 years behind.
Assuming you’re talking about Win32 API you are quite correct, the TCP/IP stack is not that bad tho (I agree that the BSD stack is better).
The “new” .NET APIs are very nice OTOH (but not very “low level”).
The QoS thing is imho just a marketing hype thing.
Yes and no. QoS is nothing new in Windows (or Linux/BSD for that matter) but apparently the new service is looking better (than “standard QoS”). As with anything MS implements they use it to full marketing effect so on that front nothing new.
Edited 2006-02-18 10:48
Assuming you’re talking about Win32 API you are quite correct, the TCP/IP stack is not that bad tho (I agree that the BSD stack is better).
True – but at the same time, its about balancing the different demands of customers and hopefully coming out with something that keeps all satisfied.
Here are some links to what is going to be changed (I can’t verify to the accuracy of those links, but
they’re interesting none the less):
http://www.microsoft.com/technet/community/columns/cableguy/cg0905….
http://www.microsoft.com/technet/community/columns/cableguy/cg1005….
http://searchnetworking.techtarget.com/infoCenter/tip/0,294276,sid7…
The “new” .NET APIs are very nice OTOH (but not very “low level”).
True, but there is also WinFX, which appears to tries to strike a mix between the benefits of both worlds – managed and unmanaged code, and as a result, deliver a much cleaner API; hopefully more ISV’s will start to take advantage of this, not only to take advantage of new Windows features but to also help reduce the costs of developing software for Windows by pushing the mundane crud off to a garbage collector and instead concern oneself about the more important things like bug squashing and improving the end user out of the box experience.
Yes, but did they add back raw tcp/ip sockets? For high performance networking, that is the way to go and they removed that feature for XP SP2.
http://www.microsoft.com/technet/community/columns/cableguy/cg0905….
Look 3/4 of the way down the page under “Architecture of the Next Generation TCP/IP Stack”, there is a picture there with Raw available in the transport layer.
“… and your lies are stupid.” ….
I can pretty much say for a fact after seeing it that the new TCP/IP puts vista 10 years ahead of BSD’s TCP/IP. Compound TCP/IP is just one thing another thing is supporting TCP/IP in hardware and then allowing it to take packets to not just multithreading but other multiprocessors it’s all done by Microsoft Research and Development team.
Let me remind you of something.
Microsoft is not publishing these articles. Some are published as a result of an event Microsoft attends, a press release, or an interview.
However, these articles are a result of the journalists actively looking for information and publishing.
Get over yourself.
Wonder if they have finally decided to get rid of any NetBEUI-based crap? Anyone know?