In my last column, I covered the basics of building Indigo applications using the PDC release of Visual Studio® .NET. Once you've learned the basics, you'll probably want to experiment with various MEPs (message exchange patterns). In this installment, I'll dig deeper into the Indigo channel types to show you how to build one-way, duplex, request/reply, and reliable messaging applications.
[...]
Ports, channels, and messages are the three key ingredients of life in the Indigo world. An application comes to life on the network by using an Indigo port, which acts as the gateway between the application and the network. Each port is identified by a unique URI known as the port's identity role. If the application doesn't need its port to be addressed by other applications on the network (e.g., the port is used only to send messages but never to receive messages), such a port may not have an identity role, in which case it is said to be anonymous.