David Chappell (not to be confused with this Dave Chappelle) recently wrote the best, most informative article I've found so far about Indigo. The article goes over the various approaches to network programming, what's wrong with the current frameworks, how Indigo solves all the world's problems (a prerequisite for all Indigo articles), and finally he covers how to migrate existing systems to Indigo when the times comes.

A few interesting points:

• Indigo is built on the various WS-* standards to ensure interoperability with non-Microsoft frameworks.
• Indigo to Indigo communication will use an optimized, binary SOAP encoding by default.
• Indigo is a very explicit framework. Methods and even data types must be explicitly added to a service contract. Likewise, service boundaries are well defined.
• Indigo services can be easily hosted in any process or by the Windows Activation Service.
• Avoid Remoting at all costs for anything other than cross-process communication on the same machine -- as I've learned myself the hard way.

Posted by JoshC at February 20, 2005 12:31 PM

TrackBack URL for this entry:
http://www.joshchristie.com/weblog/mt/mt-tb.cgi/84

Listed below are links to weblogs that reference 'Introducing Indigo' from Josh Christie's Weblog.

Name:


Email Address (not published):


URL:

Remember personal info?
YesNo
Comments: