-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pipes #1
Comments
Hmm, that sucks. Is that limitation per process or per thread? Possible solution: fork process and handle each team's tanks in different threads/process. That should get us up to ~125 tanks per team :D |
I think that's possible.. maybe you can extend that to each team's process having several processes that handle the tanks.. do you want to code it? :) |
And we have to think about the IPC... I mean... when I spawn the process, On Wed, Mar 16, 2011 at 4:15 PM, esneider <
|
The same way we do now :S with pairs of pipes |
Oh, that's right :P I'll get into that... |
there's a limit of 256 open files per process, so each process can have ~250 pipes. Since we have two pipes per child process, there's an upper bound of ~125 number of total tanks (players * tanks_per_player)
The text was updated successfully, but these errors were encountered: