Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I think that LinqToEntitiesDomainService derives from WCF classes, in which case, the following ServiceBehaviour properties might be set (either through code or config):</p> <p><a href="http://msdn.microsoft.com/en-us/library/system.servicemodel.servicebehaviorattribute.instancecontextmode.aspx" rel="nofollow">ServiceBehaviourAttribute.InstanceContextMode</a>:</p> <blockquote> <p>The default value, PerSession, instructs the service application to create a new service object when a new communication session is established between a client and the service application</p> </blockquote> <p><a href="http://msdn.microsoft.com/en-us/library/system.servicemodel.servicebehaviorattribute.concurrencymode.aspx" rel="nofollow">ServiceBehaviourAttribute.ConcurrencyMode</a>:</p> <blockquote> <p>the default is Single.</p> <p>Setting ConcurrencyMode to Single instructs the system to restrict instances of the service to one thread of execution at a time, which frees you from dealing with threading issues. A value of Multiple means that service objects can be executed by multiple threads at any one time. In this case, you must ensure thread safety.</p> </blockquote> <hr> <p>This also led me to <a href="http://msdn.microsoft.com/en-us/library/cc681240.aspx" rel="nofollow">this statement</a>:</p> <blockquote> <p>If InstanceContextMode is set to PerSession and ConcurrencyMode is set to Single, each proxy gets its own service instance. All simultaneous calls from a single proxy to the service instance are serialized because only one thread is allowed into the service instance at one time. Because only one thread is allowed into the service at one time, all other calls made on the same proxy will block until that thread exits. If you have a large number of clients that are all making calls this causes a bottleneck.</p> </blockquote> <p>So are you using a single proxy on your client, and could you create multiple ones, or is this something that is hidden from you in the silverlight client?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload