On mySimon: Oakley Juliet Polarized Lens Sunglasses
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 4 of 24:
Next »
« Previous
For THIS TCP issue MS
cannot be blamed. But MS has abused the TCP socket
prototcol implementation to reset connections for reasons
not defined by the TCP protocol state transition graph in
order to restart WEB sockets faster on its server.

Besides, MS has SO many others to be rifgtfully blamed for
that this can just pass.

-m
Posted by: michael-t   Posted on: 04/20/04 You are currently: a Guest | Members login | Terms of Use
Reply to Story Reply to Message

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Why dont we blame Microsoft for this one too  mojoman_x@... | 04/20/04
Some idiot will try, stay tuned...  No_Ax_to_Grind | 04/20/04
Hmmm....  bchesmer | 04/20/04
For THIS TCP issue MS  michael-t | 04/20/04
Microsoft users the BSD TCP/IP network stack.  B.O.F.H. | 04/20/04
That's nice to know  toadlife | 04/20/04
OSX is...  B.O.F.H. | 04/21/04
BSD Stack and Microsoft  toadlife | 04/21/04
Methinks thou dost protest...too much  escoles@... | 04/21/04
What's sauce for the goose  John Dulles | 04/21/04
Go ahead...  kray_z | 04/20/04
Most of us are safe  KTLA | 04/20/04
Are you a Mike Cox wannabe?  d_jedi | 04/21/04
WRONG!  jrbeaman | 04/21/04
[retroactive sarcasm alert]  escoles@... | 04/21/04
Get over yourself  drichards1953 | 04/21/04
Dumb Post of the Day  ShadeTree | 04/21/04
Not to mention...  rapson | 04/21/04
Time after time  ShadeTree | 04/21/04
Nice thought, but irrelevant  escoles@... | 04/21/04
It is just as likely...  ShadeTree | 04/21/04
SSafer or more prone: Both, but ultimately safer  escoles@... | 04/21/04
Unfortunately the history of ...  ShadeTree | 04/21/04
But then, history is only *what's written* (Or, 'Security by Ignorance')  escoles@... | 04/21/04

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads