This sample makes use of a WCF custom MessageInspector as described in the MSDN documentation. A message inspector is an extensibility object that can be used in the service model's client runtime and dispatch runtime programmatically or through configuration and that can inspect and alter messages after they are received or before they are sent. The sample here is derived from Oren Trutner's article “Signing Amazon Product Advertising API – C#/WCF.” Oren’s example is extended to allow all the configuration to occur in the application configuration (app.config) file. All of the Amazon helper methods have been moved to a separate library that can be used/referenced in any project. A separate console app has been included that demonstrates how to use the app.config file to configure the WCF endpoints and how to add the custom MessageInspector behavior to the endpoint.
[More]
Combining file I/O with compression can consume a ton of memory. The .NET C# compression library SharpZipLib provides excellent objects for building and working with compressed archives in memory using streams.
[More]
In this part, we examine how to use another custom text message encoder to modify the security header of a WCF message to be interoperable with a non-WCF service.
[More]
Out of the box, Windows Communication Foundation is perfectly suited for simple WCF-to-WCF exchanges. However, the diverse communication requirements of most real world applications aren’t simple. For interactions with a high-availability client application, for instance, performance is paramount. Interoperability is straightforward, if the client and service are built on the .NET Framework. For communication with an existing Java EE-based application or with diverse partner applications, however, interoperability becomes the highest goal.
[More]