So it all makes sense.

Net platform the client proxy generates three methods for every
operation listed in the WSDL document. Net platform the client proxy
generates three methods for every operation listed in the WSDL document.
Contrary to earlier claims there will be a 3.

Instead we have to actively reduce complexity and therefore flexibility.
It becomes interesting when you use a programming model that does not
have a built-in call stack. This is definitely nicer than having to use
Integer types and comparing them against null all the time. I was lucky
enough to participate in a panel on The Art and Practice of Connected
Systems, part of the architecture symposium organized by Devhawk Harry
Pierson. Configuration or Programming? We have XSLT for document
transformations, XPATH and XQuery to extract data from XML documents; we
use rules engines that are based on new languages and use BPEL for
orchestrations. Skids are always a bit tricky but this one worked out
pretty well. Configuration Progamming Now that I am back on-line I can
include a link to a dictionary entry on Configuration Programming.

Also, the tighter coupling inside a component is a non-issue because
typically one person or one team develops and controls all pieces of the
component. So is there integration work at Google?

The Visual Studio 2005 DSL tools are definitely heading in that
direction but I think we are still pretty early in the cycle.