This is the third example project in this series and is based off of the second example. This is a complete example of WCF using OO principles that leverage the NetDataContractSerializer. This example creates a number of clients that access the WCF service through multiple threads (a thread for each client). This example also demonstrates the ability of WCF to call back to clients--which is useful for "push" messaging scenarios. The zip file contains the following projects:
This is the second example project in this series and is based off of the first example. This is a complete example of WCF using OO principles that leverage the NetDataContractSerializer. This example goes along with the content found here. The zip file contains the following projects:
This is the first example project in this series and forms the foundation of the other example projects--each of which builds off of this one in an attempt to make each example easy to understand. This is a complete example of WCF using OO principles that leverage the ServiceKnowType attribute. This example goes along with the content found here. The zip file contains the following projects:
An area you'll want to take a look at when building a WCF service is service throttling. Throttling refers to the number of sessions, calls, and/or service instances that are available at any given time. Here is an example of how throttling is configured in a configuration file:
Ahhh...and now I've found what I was looking for. Thanks to Avner Kashtan's Blog, which pointed me to Aaron Skonnard's blog...
Right out of the gate, my biggest problem with WCF was understanding how to develop against a WCF service while still retaining the OO principles I've come to know and love. I really prefer to not have to change my development methodologies to fulfill the needs of whatever technology comes down the pike. For instance, I will never be fond of a technology that disallows me from using interfaces (as opposed to classes), and when I first started playing around with WCF this did indeed seem to be a problem.
Getting started with WCF is not difficult at all, but like most new technologies it might not be obvious how one goes about experimenting with it for the first time. Some of the following may change after I write this, since I'm sure there will be many additions made that make using WCF as easy as possible. Here are what I believe to be the steps required to get up and running on your machine, assuming you have Visual Studio 2005 installed: