http://winterdom.com/2006/06/wcfpoxandencoders by dæmons be driven Tue, 16 Mar 2010 06:33:03 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://winterdom.com/2006/06/wcfpoxandencoders/comment-page-1#comment-688 Steve Maine Thu, 06 Jul 2006 16:56:14 +0000 http://winterdom.com/2006/06/wcfpoxandencoders#comment-688 Fundamentally, the job of a MessageEncoder is fairly simple. It takes in some random bytes (a byte[] or a stream) and surfaces an instance of System.ServiceModel.Channels.Message up to the higher layers of the stack. How that transformation gets accomplished is designed to be opaque to the rest of the system. We think of encoders as things that freely convert between two equivalent representations of the same fundamental information set. More advanced transformations (e.g. adding/removing headers) are best done above the Encoder as layered channel. Our general rule is that an Encoder changes only the representation of the message, not its information model or contents. Fundamentally, the job of a MessageEncoder is fairly simple. It takes in some random bytes (a byte[] or a stream) and surfaces an instance of System.ServiceModel.Channels.Message up to the higher layers of the stack. How that transformation gets accomplished is designed to be opaque to the rest of the system.
We think of encoders as things that freely convert between two equivalent representations of the same fundamental information set. More advanced transformations (e.g. adding/removing headers) are best done above the Encoder as layered channel. Our general rule is that an Encoder changes only the representation of the message, not its information model or contents.

]]>