Archives
-
Combining durable messaging and workflow services: Building a custom context channel
On my previous MSDN WebCast I showed a demo of how to use a custom WCF protocol channel to combine Workflow Services and durable messaging transports channels like MSMQ. If you watch the recording of the WebCast you can see the entire demo, but there are some things that I would like to highlight about the structure of the channel.
-
WCF-WF integration in depth samples
Thanks to everybody who attended to my MSDN WebCast about WCF-WF integration in depth. You can watch the recording here and the samples are available for download here.
-
Upcoming MSDN WebCast: WCF-WF integration in depth
This Wednesday (25th) I will be presenting a MSDN WebCast about deep WCF-WF integration techniques. The session is rated 400 which means that I don't intend to spend too much time on PowerPoint :). Instead, I am planning to cover in depth (meaning code...) some of the WCF-WF extensibility mechanisms that facilitate the integration of those two technologies in real world scenarios beyond just Workflow Services. In terms of features, I plan to talk about Workflow Services (of course), Durable Services, Security (lots of things here), Dependency Injection, Durable Messaging, Routing, Filtering and more depending on the timing.
-
Describing RESTful services using WSDL 2.0
I've spent a few minutes last night reading this "how to" guideline from IBM, I have to admit that for a while I was affraid that somebody was going to come up with this idea but I really thought that we, as a community, were pass this stage of understanding the fundamental concepts of REST. This is REALLY REALLY bad. In my opinion, the first assumption that is wrong is to assume that RESTful services can be described using the same artifacts that we use to describe traditional Services. I agree that WSDL 2.0 is a HUGE improvement over WSDL 1.1 but it is still a RPC (in the broad sense of the term) type language with constructs like interfaces and operations which makes it less than ideal for modeling RESTful services which are based on a completely different domain with artifacts like resources, relationships, URI templates, etc.
-
I survived Teched
Well I didn't have any time to blog during Teched (by the end of my last talk I was completely exhausted and I still had to work at the booth with my friend Clemens Vasters) but I survived.