Tuesday, February 06, 2007
« TextMate for Windows | Main | Getting in bed with Google Reader »
Harry Pierson has an interesting post that outlines how he learned to stop worrying and love WCF. In the post, Harry talks about the concerns that he's had regarding the lack of support for long running services in Indigo, and then discusses how a talk with Shy Cohen helped clarify some of the misunderstandings that he had. The primary of which, is that WCF's solution to long running services is Duplex Channel. In fact, Shy confirmed Harry's feelings that WCF doesn't have a real answer to long running services in v1.0.

I found the post particularly interesting since we've been talking about how best to support long running services within our application. One option that we've considered is Duplex Channels, however, we've had some concerns with whether or not the Security folks at our clients would be ok with us opening up a callback channel from the desktops running our software. At any rate I'm interested in what others think would be the "Reese's Peanut Butter Cup of service messaging". Harry's would be "something that has the programming semantics of SSB and the interoperability of WCF". And you?
Wednesday, February 07, 2007 4:12:59 AM (Eastern Standard Time, UTC-05:00)  #    Disclaimer  |  Comments [2]  |  Trackback Related posts:
Cool WCF and SOA Tips
Why is my IsOneWay operation blocking?
Tracked by:
"Morning Coffee 33" (DevHawk) [Trackback]

Wednesday, February 07, 2007 1:01:13 PM (Eastern Standard Time, UTC-05:00)
Personally, I'm looking very closely at the AMQP protocol; queued messaging systems are da bomb! :)
See my full comment on Harry's article here: http://www.winterdom.com/weblog/2007/02/07/LongRunningServicesAndWSRM.aspx
Wednesday, February 07, 2007 1:56:49 PM (Eastern Standard Time, UTC-05:00)
Tomas, I definitely agree that queued messaging is where it's at in service oriented applications. I haven't read much about AMQP so I'll have to do some digging to learn what its all about.
Name
E-mail
Home page

Comment (HTML not allowed)  

Enter the code shown (prevents robots):