Hi, Can someone clarify whether my understanding of the Worker and Engine is correct. Particularly with respect to the case of having a separate worker process, from the main engine controls.
Does the separate worker process 'know' what workitems to carry out because the engine writes & dispatches this information to the storage? The worker is then monitoring the storage for this information? What code does the worker actually execute, compared to the process that controls the engine? For instance within my rails ruote initializer, i am defining storage_participants in a block that doesnt get run if it is initialized by a rake task. As set out by ruote-kit: unless $RAKE_TASK # don't register participants or set up AMQP in rake tasks ... set up participants here. end So I take it the worker does not 'know' about participant definitions, in which case which process executes custom local participants? I have read the various pages on the ruote site and browsed the source a bit but am still a little confused about how it all works. I'm having to use a separate worker process because when running tests with ruote as a single process the test-process dies after completion and kills the threads spawned by ruote. This leaves the storage in a fragile / sometimes broken state. It would be really useful to have a diagram of the basic program flow, when running a separate worker process. -- 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
