Sorry just an addition to this: In summary what would be the way to have a multiple worker capable store that is not blowing up with excess data that is not essential to the ruote engine/workers?
Thanks, Michael On Tuesday, July 24, 2012 12:38:11 PM UTC-4, Michael Papile wrote: > > Hello, > In the default history I see "By default, the history is an in-memory > history (see Ruote::DefaultHistory) (and it is worthless when there are > multiple workers)." Now I am using the redis storage in order to run > multiple workers. I am not interested in the large amount of history made. > Does this just mean that *History* will not work for multiple workers, > or does this mean that other information critical to the ruote workflow > will be affected? I do not mind if the history does not work as I am not > interested in it. > > Thanks, > Michael > -- 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
