<ChristophDotNet

Did anybody else catch this? Over the past three weeks, there were two announcements that indicate a rather large shift in how Microsoft view's the role of service orchestration:

To continue Jeff's and my musings on Aspects...

Now, if you own the web service interface then the second advantage bullet is less important and aspects may not be important to you. In those cases it seems to make sense to skip the orchestration unless you assign a high value to having a consistent design pattern. You have to weigh if you need down-to-the-metal performace (then why are you doing web services?), or if scalability is really what you are after. That's where the role of the service architect comes in, to help you make those trade-off decisions.

Kirk Allen Evans and Paul Wilson are investigating some strange behavior that Paul found using the XmlSerializer.

For those who haven't seen the paper for Eric Meijer's presentation on the Xml-based-programming-language-formerly-know-as-X# at Xml 2003 (and of course for me to save the link in a place where I find it):

It was announced last October ... it's finally released: WS-BusinessActivity, the WS-* spec for long running business transactions. MSDN also put up a new article explaining how the various transaction related WS-* specs relate to each other.

Follow the instructions at:

I was quite intrigued by the idea of providing a research service for office. After all, this was the first real-world web-services based extension interface for a major application. I downloaded the Microsoft Ofiice 2003 Research SDK and got going.