On Jun 4, 2:36 am, John Mettraux <[email protected]> wrote: > I'm not sure about this /participants tab/resource yet. I'll think > about it, maybe a #info method returning a hash of "information" about > the participant and its current status. Maybe you have a better idea.
The current status and a hash of info (type, in which process they're invoked, a small description if it's been provided...) for each registered participant, that sounds enough for me to begin with. For block participants, a link to the code could also be useful (as it is to see process definitions), so one can check what it does exactly (probably useless for a regular user, but a nice shortcut for debugging ...), but if it implies separating each participant in it's own file, I'm not sure this is a good idea. These are the only few things I can think about now. Thanks again for your time. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
