So it looks like Silverlight 5 will solve the UI thread issue. They mention a low-latency networking mode, however, if there weren’t caveats, why do they make it sound like something you have to turn on? Wouldn’t you always want a low-latency mode?
What is sounds like to me is that this new low-latency mode has some other hidden costs involved. It will be interesting to see what these are, and what the threading model is for the new stack. I’m truly hoping it doesn’t mean a single thread for networking and will allow us developers to choose.
Advertisements
My guess is the network IO / UI will still share a common thread, however network IO will take priority over rendering when this mode is enabled.
Just read some more… it does say it uses a background thread. Interesting. Perhaps the new network stack is not 100% backwards compatible, hence the “mode”
Looking forward to a beta. Want to test the mode out.
Do you have a link for where you read that?
http://www.microsoft.com/silverlight/future/
Click on “Business Application Developement”
“Silverlight 5 performance improvements include:
Reduced network latency by using a background thread for networking.
XAML parser improvements that speed up startup and runtime performance.
Support for 64-bit operating systems.”
It’s marketing speak, so take it with a grain of salt.