Hi John, > yes, this was convoluted and the solution was one good night of sleep.
Ah, sleeping is often the key to many problems! > It's just to give some breathing time to the engine, with fast storages this > is too much, but with a storage like ruote-couch or if you're encoding mkvs > in the background, it might be necessary. Since I run the tests with all the > storages, I go for a safe value. Thank you for the explanation. > Speaking of things occuring at different paces, I think there might still be > an issue in the current implementation : what happens if engine A just > launched wfid0, and engine B stumbles on My project requires a single engine. I feel safe against such a scenario, but the problem exists, yes. Instead of iterating in the hope to get a unique name, how about having launch_single also store the engine name aside the wfid ? Eric -- 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
