Talk:RoboRumble/Contributing to RoboRumble/Multi-threaded Rumble Client

Clever! But I wonder if you will run into file locking issues: both the executor and uploader processes will want to write to results1v1.txt (or resultsmelee.txt etc). The executor is trying to add results and the uploader is trying to delete them... Do you know if priority battles will still work? (it might) --Darkcanuck 15:07, 8 April 2009 (UTC)

Good point. I'm not sure. This can result in duplicate result uploaded or losing result, right? Actually, this article is meant to use with newer, not-yet-supported roborumble client, as current version is not that fast to require seperate uploader, but newer version (1.7.1.1) is. I can tell you that on my machine, each (nanobots) battle fought in less than one second (for first few iterations) so uploader probably can't upload them fast enough due sleep(1); :-) I'll see if I can patch it more clever. » Nat | Talk » 00:52, 9 April 2009 (UTC)

You could get around this by modifying the rumble to write each result to an individual file in a results directory. Then the other one just reads in the files one at a time. But that requires modifying the source code. Very clever way of using the rumble =) --Skilgannon 06:09, 9 April 2009 (UTC)

Nice idea! I'll try that. » Nat | Talk » 09:23, 9 April 2009 (UTC)

---

Should we moved this page? The title is very, really long. » Nat | Talk » 09:23, 9 April 2009 (UTC)