Hello Ron,
I have listening and studying most of the things you have been involved with for the last 4 years. Starting from the blocks, webcasts, etc/ and now the arccasts.
It seems to me that your presentation skills have improved quite a bit so I wanted to congratulate you for that. Honestly I did not like all that fake and fun stuff that you use to do a little bit too much before, now it seems to be a good mix, I agree with you that things should not be taken too seriously because then we forget about how much fun it is to do it. But the content and the information you provide have been very valuable to the companies I have worked for and myself, so thank you very much.
The reason of the present is to ask you for contact information for Danny Boyton (name speeling as well), the person you interviewed in this arccast. It seems that him and I have taken very similar paths when it comes to architecture.
Since before PDC in LA I have been wondering about workflow and Coarse Interfaces common to xml web services. I see work flow as a visitor pattern to many applications probably provided as an xml web service in itself. It seems to me that workflow foundation works better with finer granular interfaces in particular when you want to handle transactions and all that. I did not get a chance to implement the workflow visitor pattern concept I had in mind, but It is still something I want to figure out completely. Id did get to develop a workflow as a service utilizing strongly typed datasets as the state machine, it works very well and it is easy to visualize. The dataset not only provides the state but also a dataset derived class provides the engine, that can be consumed by any lager.
So there it is, workflow as a visitor is mostly and important visitor that captures and provides information that help the business logic control its own transactions (because of coarse granular interfaces, the buisnes logic does quite a bit). Yes the workflow controls long-lived transactions whose roll back procedures are not left to the underlying structures (ado.net, .net framework, sql server, etc.) but to the workflow itself and to additional business logic.
Anyhow I would appreciate very much if you provide me with Danny Boyton's contact information. I am not even sure how to spell his name; after all it is an arccast.

right?
Thanks Ron and keep up the good work.
Cordially,
Luis G Gonzalez
self proclaimed enterprise architect, systems architect, and applications architect.