Posted in Uncategorized, tagged concurrency, IIS, WCF on August 14, 2008 | Leave a Comment »
Recommending the post “WCF Request Throttling and Server Scalability“.
It contains important information regarding WCF’s asynchronous processing when hosting on IIS. For example, I was unaware that
So in the release of .Net 3.0 and 3.5, WCF implemented synchronous versions of HTTP module and handler instead of asynchronous ones
meaning that even with asynchronous service implementation (asyncpattern=true), a [...]
Posted in Uncategorized, tagged concurrency, WCF on July 11, 2008 | 1 Comment »
This is the third in a series of posts about the AsyncPattern in WCF.
The previous two posts described the purpose and usage of this property on the service side. The present post addresses the client side.
AsyncPattern at the client side
The AsyncPattern=true is used at the client side to expose an asynchronous programmatic interface to a [...]
Posted in Uncategorized, tagged concurrency, WCF on June 28, 2008 | 1 Comment »
This is the second in a series of posts about the AsyncPattern in WCF.
The previous post described the consequences of setting AsyncPattern = true on an OperationContractAttribute.
However, a question still remains: when and how to use AsyncPattern = true on the service-side?
When?
The WCF documentation states that
“Use an asynchronous approach in a service operation implementation if [...]
Posted in Uncategorized, tagged concurrency, WCF on June 27, 2008 | 2 Comments »
The OperationContractAttribute is used, in WCF, to define operations on a service contract. This attribute contains the AsyncPattern property that can be used to implement or use services asynchronously.
AsyncPattern at the service side
Consider the following excerpt
1: [ServiceContract]
2: interface IService {
3: [OperationContract]
[...]
Posted in Uncategorized, tagged concurrency, WCF on June 10, 2008 | 1 Comment »
In an older post, Nicholas Allen stated that an asynchronous delegate invocation on a WCF client channel object will block until the response is received from a service.
The only given explanation was:
The problem is that BeginInvoke knows about and only works with specific types of proxy objects, which do not include the proxy objects [...]
