I would make it configurable, say in config.ru (perhaps per participant type? That would probably make things too complex). I can think of at least one case where you might want more than 24 hours: interactive participants. So you call the participant, it notifies a user of some action that needs to take place, and doesn't reply until the user performs the action. In some use cases the user might take several days from the moment they receive the notification to the moment they perform the aciton.
-Mario. -- I want to change the world but they won't give me the source code. On Wed, Oct 5, 2011 at 00:49, eric smith <[email protected]> wrote: > Hello John, > Sorry for not getting back to you sooner, and yes I think a 24 hour > window will work. I can't think a case where a participant would take > 24 to run. > I was also thinking it would be nice to have the memory size of the > worker in worker_info, but now I am probably pushing my luck. > > Thanks > Eric > > > > On Oct 2, 6:10 am, John Mettraux <[email protected]> wrote: > > Hello Eric, > > > > I'm still working on {pause|resume|stop}_workers, it's currently in a > > local branch, looking good, I just have trouble finding time to work > > on it, but I hope by the end of the week. > > > > I was thinking about the worker_info, would it be OK if I wiped info > > about workers that haven't replies in the last hour (or last 24 hours) > > ? I don't wont this list to become 99% dead workers. > > > > What do you think ? > > > > John > > -- > 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 "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
