I'm prototyping some of my work-related architecture designs using .Net 3.0 Windows Communication Foundation (WCF)-based applications talking to each other over the .Net Service Bus. It's a pretty nifty way to communicate among applications running on different machines without having to know the actual addresses of those machines. And WCF and the .Net Service Bus handle all of the communication layer stuff for you, so the developer can concentrate on what they developer's field of expertise. In other words, a developer can concentrate on the the data and services at hand and effectively ignore the underpinnings required to connect and transport the data to the services. WCF works by agreeing on things like a ServiceContract and a DataContract and on interfaces implemented by the classes that are service contracts. So what did I learn today? Although in normal programming an implementation of interface you can give different names to the same method parameters in a method's signature,... - Craig Eddy