views:

93

answers:

3

Am reading an O'Reilly book called "Learning WCF" and in chapter one, it mentions: For example, services can be accessed over a variety of supported protocols, including named pipes, TCP, HTTP, and MSMQ.

And now I can't help but wonder... Named pipes, HTTP, TCP and MSMQ and what other protocols? Didn't they just mention all protocols that are available for WCF or are there more protocols available, but not mentioned?

And how to use those other protocols? And is it possible to even add more protocols?

+3  A: 

The point is that WCF is extensible - you could write your own custom bindings to use custom protocols. People have for example written in-process/null transport bindings.

Out of the box, I agree that this pretty much covers it (you might want to consider HTTPS as a separate protocol, maybe not).

David M
+1  A: 

For the serialization format, you can also use protobuf-net, a .net implementation of Protocol Buffers.

Winston Smith
Interesting option. :-) The Wiki page is still a stub, though. It could use more information.
Workshop Alex
@Alex, see http://code.google.com/apis/protocolbuffers/docs/overview.html
Winston Smith
+1  A: 

Yes that covers all the transport channels that comes out of the box. You can implement custom channels, like this example at MSDN, where a UDP channel is used for WCF.

It is also possible that the word protocol is intended to be interpreted as all variations of application layer protocol as well. e.g. BasicHttp, WSHttp, WS-* etc.

Pratik