This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Sync me up, Scottie
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
Dan Creswell questions whether RPC must equal synchronousity and shows RPC-style code which demonstrates true, async-style interaction (with Return-Address pattern).
And I must agree with him. You can create duplex communication by explicitly using two one-way channels. What I don't like is that I have no way of preventing things I consider bad, like sync-req-response in this manner.
I also don't like having to implement an interface (whatever that means in the distributed sense) in order to handle some message that returns to me. Not to mention that the tools today would probably try to bind me to some specific endpoint to get this to work.
WSDL doesn't express these kinds of interactions. SSDL looks promising, and I'm wondering what's going on with SSDL2 which Google has barely heard about. Bottom line, I'm looking for a different semantic than code - something that was designed for communication, not general purpose programming.
Previous Topic
