title: Tic Tac Toe AppEngine Channel sample mechanics
body: <p>Greetings gents,</p>
  
  <p>EDIT: forgot the link to the sample, here it is:  <a href="http://code.google.com/p/java-channel-tic-tac-toe/source/browse/trunk/src/com/google/appengine/demos/channeltactoe/" rel="nofollow">http://code.google.com/p/java-channel-tic-tac-toe/source/browse/trunk/src/com/google/appengine/demos/channeltactoe/</a></p>
  
  <p>So i'm studying the channel API of AppEngine and i stumbled onto a question regarding the way it's architecturally  coded. They way i perceive it works is the clients send standard POST requests, the game gets updated and the both players get the update through the ChannelService a JSON message.</p>
  
  <p>Now i read on the javadoc that Channel is a two-way communication channel, so why did this developer go for the POST servlets(for game-updates) and Channel for distribution instead of using a single servlet for the sole creation of the Channel and then using that channel for front and back game updates communication between the client and server?</p>
  
  <p>To summerize, what did does this architecture gain over using a true 2-way channel, or is it even possible to use the 2-way(back to server channel) in that way.</p>
  
  <p>Thank you for reading, i hope my question is valid/understandable.<br>
  -Rohan</p>