Hi Don and Colleagues:

Thanks much for the example. At a quick scan, it looks like it'll take some digesting to get my head around. I'll give it a closer look when I get the chance.

Don, you need to read the code along side the slides. I will probably be giving a revisted version of the talk in early May. I will annotate the example in the week to follow. However I need to change the code somewhat so it is a wee less confusing to a newbie and gets rid of a design flaw concerning daemonisation. With the current programme, if you hit the processor fast enough, you will get back 404s. These really should be 500s. This is not a problem with the technique but with my simple minded implementation of the WS-BPEL specification that warns of race conditions associated with certain activities. Although fine for my purposes, I should conduct two sets of tests 1) More feature torture tests where I test non-trivial message exchange patterns. 2) Performance tests. Test against - Apache ODE - A Stackless /Twisted solution that does not spawn a server instance in a tasklet - A pure Twisted solution - A Twisted solution that uses inlineCallbacks. Cheers, Andrew ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com