Isn't this just a re-hashing of the difference between TCP and UDP? It almost seems like it will replicate UDP in hardware. For things like streaming media and VOIP you can loose a couple of packets here and there without noticing any loss of quality so things like that typically use UDP because it doesn't bother to go back and re-send those lost packets it just keeps going, while TCP will panic and wait untill it receives every bit of data. There is certainly a need for both TCP and UDP connections depending on what kind of data you are working with, so if it is in fact just recreating a UDP like connection how will it work when sending data that absolutly requires that every packet get to its destination.
Sony's just released a 15.5-inch addition to its VAIO S Series that not only adds a crucial bit of extra display acreage, but also bumps things up to a full 1080p.
The most commented posts on Engadget over the past 24 hours.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
Isn't this just a re-hashing of the difference between TCP and UDP? It almost seems like it will replicate UDP in hardware. For things like streaming media and VOIP you can loose a couple of packets here and there without noticing any loss of quality so things like that typically use UDP because it doesn't bother to go back and re-send those lost packets it just keeps going, while TCP will panic and wait untill it receives every bit of data. There is certainly a need for both TCP and UDP connections depending on what kind of data you are working with, so if it is in fact just recreating a UDP like connection how will it work when sending data that absolutly requires that every packet get to its destination.