title: (C++) Game Server, (Flash) Client
body: <p>I'm interested in putting together my first online game using Flash as the client and writing a back-end application in C++ where the actual game state is kept.</p>
  
  <p>I've done lots of games in C++ before using SDL, SFML, Allegro, etc etc but never gotten around to using the network libraries. I was just interested in some helpful direction for which libraries are best suited to game servers where the actual server doesn't have any graphical display (or doesn't need to but could have). In all honesty I think the answer will be <em>any</em> and once I get the hang of sockets it'll become a breeze sending data back and forth... but it can't help to ask first.</p>
  
  <p>I have very little experience in flash or as3 but like the idea of being able to access the game through a browser - learning flash is obvisouly going to be an obstical that I'll have to overcome but my main interest again is any tips on libraries, or sources, or tutorials that are good for sending/recieving data via sockets or whichever method works best.</p>
  
  <p>I've read about the arguments between TCP/UDP so I don't want to start a war like that here; just general helpful advice please - I'm only looking for something simple to get me up and running :-p</p>
  
  <p>As a side note, the reason I'm choosing C++ is because the players are actually robots with minature virtual-machines and everything will run on the server so as the player count rises so will the need to emulate each and every vm :-p</p>
  
  <p>Update:</p>
  
  <p>The game world is intended to be real-time, but the interaction of the player doesn't have to be. The basis of the game is that you program little robots that interact in a persistent world and have goals and challenges to meet on a daily/weekly basis to earn points.</p>
  
  <p>I was thinking that buffering the display data would be possible as the player doesn't need real-time visual as they have no direct control of their robots. The server would buffer up 10 seconds or so of data for each connection and then ship it out in one go - this way while the data is being played back in the client the server is busy buffering some more.</p>
  
  <p>The general interactions the player will have with the server will be uploading new code and getting statistics, there may also be other one off commands to move your robot around or reset it to a starting position. Any remote control is done through a communications channel and thus is delayed by the buffer. This could easily be explained by the fact that the persistent world is somewhere like Mars (the planet) and the signal takes a while to go back and forth.</p>
  
  <p>I was planning on having a "lab" whereby you could set up the robots and test them in realtime on the client, this has nothing to do with the actual game world and thus shouldn't require any networking - although I don't fancy writing a VM in both languages :(</p>
  
  <p>I'm completely comfortable in C++ and have some working prototypes of the persistent world in place already - I'm just a complete newbie when it comes to networking so figured it'd be best to get advice first.</p>