Just pointing out this posting: Is Indigo compelling or boring

It's an interesting one and I think I'm pretty much in agreement. My dream around Indigo from what I've seen so far is that "down the line" the distributed technology decision for the MS platform will be a "no-brainer" in that you'll select Indigo and design your application with it. At some later point you'll deploy your app and configure what kind of transport you want, what kind of security you want and so on.

What's the main advantage? For me, it's the reduction in the complexity. Today, you need to have so much stuff in your head to make a decision about how to build a distributed application on the MS platform. There's a whole host of technologies from things like socket programming, dcom programming, enterprise services, remoting, asmx web services, wse web services, message queue programming all the way up to things like BizTalk adapters and pipelines and SQL Server Service Broker queues.

I don't want all that stuff in my head. I just want to learn one API for separating 2 pieces of software across AppDomain, Process, Machine, Enterprise boundaries and leave it at that.

That's what Indigo promises to me and so, yes, it's very compelling :-) As the original post suggests, if Indigo fills the communication gap then maybe we can liberate a whole bunch of time to think about more interesting things ;-)