I am in the process of spec'ing out a new ruote project. The idea is to have a daemon-kit based ruote engine running which is then managed by a workerless ruote-kit (with some extensions) admin console. Both the engine and admin console will be running off the same FS storage.
Initially I was going to define all the participants and processes in the engine however that is causing a bit of a snag as the admin console would then not have any knowledge of the process definition so that the process may be launched dynamically. One strategy I thought was to define all participants in the engine but define the processes in the admin console. Another was to save all the process definitions as class constants and package them up as a gem. Is there any best practise in the Ruote community about persistently storing/loading process definitions? -- 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
