I finally had the chance to meet Steve Maine of Windows Communication Foundation (WCF, codename "Indigo") fame face-to-face. While Steve and I actually worked "together" for most of my Avanade career we hadn't met, and it was one of my objectives at the PDC to rectify that.
Thanks to Matt Joe we met at the Ask the Experts session Thursday night and we had an interesting discussion regarding the WCF "messaging paradigm". It came up in the context of a discussion regarding the Service Activity Generator. One of my positioning statements for this utility is that many developers don't want to - or need to - think about the messaging infrastructure that the WCF declarative model hides under the covers. Steve, on the other hand, said that the product team is actually re-thinking this model and may want to have the developer be exposed to more of the messaging paradigm.
Consider the following approach:
>> Construct request message
>> Submit request message to service
>> Receive response message
>> Parse response message to retrieve "interesting" data
vs. the following:
>> Call service method and receive "interesting" data as the return value
Which do you prefer? Particularly when building a composite application, when you're going to use this paradigm dozens, if not hundreds, of times.
I'd like to invite Steve to respond here to see if we can get some interesting dialog going on the topic. Here's your chance to potentially influence a product direction, so jump in!