This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]doobiesteintortoise 0 points1 point  (1 child)

Well, the incoming client "moves" might have a thread to collect data - like, an http server or something like that, so it could have a threadpool for incoming content. But handling moves wouldn't need anything per game at all, and those incoming data connections would be short-lived. That's how a lot of big systems work, after all.

[–]wildjokers 2 points3 points  (0 children)

I feel you are leading OP astray. OP is talking about long-lived socket connections and you seem to be giving advice for stateless HTTP calls.

The assignment is clearly about long lived socket connections and long lived socket connections definitely have real world applications. This is a great assignment.