Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In my opinion the best strategy to approach a turn based game such as this, is to decide on some basic architectural approaches. Diagram out the componenents and some basic game flow diagrams.</p> <p>You should put the bulk of the game engine logic in the server component. The clients should be kept as thin as possible, focusing primarily on</p> <ol> <li>Communication with the game engine</li> <li>Accepting user inputs</li> <li>Interpreting game engine responses</li> <li>Drawing the screens</li> </ol> <p>Your server/game engine should be relatively stateless, yet maintain a list of current game sessions in play. Stateful SOAP web services or even HTTP Servlets would be a good choice because they maintain session for you by placing and reading session cookies in the request.</p> <p>Everything web works on request response so it is by nature stateless, but certain technologies like Java servlets will help you maintain sessions so that you don't have to. No need for physically creating seperate threads, each request causes the application server to spawn a new thread of execution, while the session by nature is volatile.</p> <p>On the server side I would persist all data for a particular active game in the session. In this way, your game engine will maintain the orderly communication between the two players.</p> <ol> <li>Player 1 sends end of turn request with all of the game state change information.</li> <li>Game engine interprets request, makes necessary changes to the game state.</li> <li>Player 2 sends frequent requests to check and see if it is Player 2s turn yet.</li> <li>Game engine acknowledges Player 2 request for its turn and sends the new game state in response.</li> <li>Player 2 receives the response, updates its copy of the game state making note of the changes since its last turn.</li> <li>Rinse and repeat.</li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POJava Client/Server turn based help
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmaple_shaft
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJava Client/Server turn based help
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for the help! Most of what you said makes sense, im just a little confused as to where the servlets would come into play.
      singulars
      1. PO
      1. USBthunder
    2. COServlets play the role of the server essentially. They are requested for information or information is posted to it. It is necessary because the applets can not talk to each other directly. Think along the lines of playing Starcraft on Battle.NET. There are many players in a single session/game and Battle.NET is the server. Each player is constantly sending information about what they are doing to Battle.NET and in response Battle.NET sends updated information about other players. Don't confuse the server and the host. The host is just a player who initializes the params of the session.
      singulars
      1. PO
      1. USmaple_shaft
    3. COThis is pretty heavy stuff so don't get discouraged. Before you delve into a servlet and what it is capable of you need a FIRM grasp of HTTP communications. There are countless tutorials online to teach you this. When you understand that paradigm you can delve into making simple servlets, ie request a web page, return HTML response. Then you can get into more advanced servlets like serializing a Java object into an HTTP request, and deserializing a Java object from a servlet HTTP response.
      singulars
      1. PO
      1. USmaple_shaft
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload