Asynchronous WCF Calls from Silverlight

I noticed that you can only call the WCF service from Silverlight asynchronously. This seems like pretty good practice, especially when deploying over the Internet, but I wonder why this restriction was placed on the architecture. Is this solely to ensure good practice or are there technical reasons for this?

+4
source share
1 answer

In essence, this is because Silverlight is launched in the browser window of the Window. This means that if Silverlight is waiting for a response synchronously - at this time the entire browser window does not respond.

In addition, Silverlight initially (Silverlight 2) had only a client browser communication stack.
This means that all communication in Silverlight has been routed through the browser.
Browsers do not support synchronous programming models for communication.

This is less of a problem with the communication glass with the Silverlight 3+ Non-Browser Client, but it still makes sense to keep this programming model in place.

+8
source

All Articles