I need to interoperate new WCF products with our existing TCP and UDP based messaging products, starting with TCP.
Do I need to create an entire custom transport channel from scratch, or can I just use a custom MessageEncoder with an existing transport channel
The issue has to do with the fact that each Message in WCF is based on Soap/Xml. The byte streams coming in from and going out to the legacy systems are not Soap/Xml, but proprietary byte streams.
I am looking for the "easiest" solution for now (e.g. inheriting from WCF base classes and/or changing properties/encoders in transports that ship with WCF), with plans to expand the solution to be more robust in subsequent iterations.
I am working my way through the January CTP examples, but have yet to find a service example that does not assume its clients know something about Soap/Xml.
Thanks in advance, Greg
WCF interop with legacy TCP and UDP clients
Freek Bos
Did you find a good example/code for using WCF to service legacy/binary tcp clients I'd kill for a code-snip.
Thanks!
James
ocanon
Greg, if you write a custom MessageEncoder, you can encode as any format you like, even if you don't use SOAP or XML. For a non-soap sample, check out Vipul Modi's Yahoo POX client: http://windowscommunication.net/ControlGallery/ControlDetail.aspx Control=2222&tabindex=2. He happens to be sending XML over HTTP (no SOAP), but you could send arbitrary encodings over without a problem.
Steve Maine also wrote up an SMTP channel for WCF that you can download from his blog: http://hyperthink.net/blog/2005/11/13/SoapSMTP+For+Indigo+Beta+2.aspx.
Best regards,
JJustice [MSFT]