Hi John, Thanks for your prompt reply. No problem... :-)
I made a very minimal version of the workflow application I'm currently working on, with all the participants stubbed out: They simply return an ok. I put this application on Github, so you can try it out for yourself: https://github.com/suhrawardi/ruote_poc You can run the bin/test.rb script to start the workflow (see the README.md). The first command line param is the number of workflows that is started. In the bin/app.rb file, you can change the nr of workflow engines that you want to start to handle the requests (within the same process). In order to handle the requests with multiple processes, just start bin/app.rb a few times. For me, there is not much difference whether I run the application with multiple engines, a single engine, or handled by multiple processes. Besides that, there is no gain when I switch to another storage implementation (which you can change in lib/yaap/engine.rb). Mind that there is a 'progress' key in the workitem hash that is dumped by the test script. It is really weird, but some steps seem to be started and finished more then once... While that should not be the case (workflow is in participants/yaap_mobile_auditor/workflows/main.conf.rb). Hope you can help us pinpoint where the problem is. If you have any questions, or like me to try something else, please let me know! :-) Thanks a lot so far! Jarra -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
