Hello John, Thank you for your response. My replies are inline:
> If I go once again over your "I would prefer" sentence: > >> but I would prefer to let the primary app manage >> the process lifecycle from launching a process, > > covered by > > Dashboard#launch(pdef, fields) I'll try to describe in better detail what I want to achieve. I have an interface that lets users manage resources based on a set list of predefined process definitions. For example, a user needs to execute a command on a remote server. She provides a few parameters: the hostname, her credentials, and the command she wants to execute. She submits her request to the system, which retrieves the correct process definition and sends it along with the user's parameters (as fields) to Dashboard#launch. The user lives completely outside of ruote. She has no knowledge of route nor is she is a participant in the ruote process, but she does require knowledge that her task is complete. Thus, what I need is a supervisor/launcher/reactor that 1) takes her request, 2) submits the process to ruote, 3) knows when the process terminates, and 4) responds to her when the process completes or fails. I've tried doing this with #on_terminate/#on_error participants, however I would much rather have dispatch and response happen externally to ruote. >> tracking its progress, to > > covered by > > process_status = Dashboard#ps(wfid) True, I use this method to check on process state while the process is running. > or by inserting "checkpoint" participants or observing checkpoints. > >> ultimately responding to the workitem results once the process completes. > > Usually done by placing a "last step" participant or by using an > on_terminate. > > ( > note: did some work with Hartog on process observation: > > https://github.com/jmettraux/ruote/blob/master/lib/ruote/observer.rb > > https://github.com/jmettraux/ruote/blob/master/lib/ruote/util/process_observer.rb > > maybe this could help > ) > Thanks so much for pointing this out. I found https://github.com/jmettraux/ruote/pull/54 and read the discussion surrounding it but the pull request was closed without being merged. The ProcessObserver is actually very close to, if not exactly, what I need from ruote to implement a supervisor. --- Dan -- 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
