Thanks Ashley. Not a bad idea for a quick prototype of the server, but the real version would need to handle authentication, persistence to DB, transaction & payment system integration, load balancing etc. If you ever decide to make server side api or protocol definition, let me know! The solution for this kind of thing I think is just to use your existing socket api, but then we lose out on the sexy features like lag handling. its not for a run around and shoot type game, its for a bingo type game, but the key is that the balls appear at the same time for all clients etc. which is always tricky.