[ServiceOperation]? Where's the message?

When you look at a simple Indigo "Hello, World" sample, you'll see that it follows the RPC style; the client constructs a proxy that implements an interface, it calls methods, magic happens on the wire, and the equivalent methods get called on your service object. The SOAP message purists are, I imagine, crying out: "but where is the message!?"

Well, the message is there; but over the past few years of evolving Indigo, and getting feedback on it, we've found that when using a language like C# that has objects and methods as its native constructs, the easiest, most accessible way of exposing our distributed services is via (you guessed it) objects and methods. However, the message is there if you want it:

[ServiceContract]
class Sample
{
      [OperationContract]
      public string Hello(string name)
      {
            Console.WriteLine(OperationContext.Current.IncomingMessage.ToString());
            return "Hello, " + name;
      }
}

If you want to be even more explicit, Indigo also supports a programming model something like this:

      public string Hello(Message m) {...}

Perhaps I'll go into this in more detail in the future, as well as some other alternatives Indigo offers in the continuum of APIs between RPC and strict message-passing; let me know if that would be interesting.