WF RFQ/RFS Negotiation Thoughts
I’ve missed reading the last three issues of MSDN Magazine, so this morning I printed the interesting articles to read for my daily commute:
- Cloud Gazing From Silverlight 2
- Browser Interoperability In Silverlight 2
- Silverlight 2 Transforms And Clipping Regions
- Best Practices For Windows Workflow Foundation Apps
- Render Text On A Path With WPF
- Thread Management In The CLR
- WCF And WF Services In The .NET Framework 4.0 And “Dublin”
- When Things Go Wrong
- An Introduction To RESTful Services With WCF
- Managing Dynamic Content Delivery In Silverlight, Part 1
- Round-Robin Access To The ThreadPool
Mixed in with the expected Silverlight articles are a few WF articles. I’ve been looking at WF for a number of reasons recently. I came across Guy’s (now dated) posting on WF/WCF which shows ReceiveActivity in action. Matt has a screencast on using a WCF Receive Activity in a workflow here.
ReceiveActivity is interesting since it could be used from the perspective of RFQ/RFS. If you consider “negotiation” as detailed here, then it probably wouldn’t be hard to envisage a Silverlight RIA talking to a WCF/WF (Dublin) server that facilitates the RFS negotiation, coupled with an initial limit/credit check at the beginning of the negotiation.
Outstanding questions: How would the WCF/WF work in a load balanced configuration, and likewise for fail-over. What to use to return to async responses from the WF server to the RIA.
Hopefully in the next few weeks I’ll begin to build some of the above as I’m curious as to the performance of WF in the above scenario.