TicTacToe - Two party interactive

The data flow pattern is two-party interactive (see Figure 2b). The TicTacToe application exhibits this pattern. After the first player makes his move, it is the second player's turn. The two players alternate until some player wins or the game ends in a draw. The application uses a TicTacToe GUI component to display the state of the gameboard. Note that the application requires that the gameboard be continuously displayed while the game is being played.

NetPebbles:

The NetPebbles script creates component instances at the players machines during the first exchange of moves and these components persist as a part of normal NetPebbles execution. They display the game board. The NetPebbles runtime transfers the game state between the machines while the game is being played as a part of moving the script program state.

RMI:

TicTacToe ``Impl'' servers are started on the players machines and the client controls the game by invoking appropriate methods on the servers.

Aglets:

Since Aglets do not support persistence of component instances, persistence is simulated using slave agents. The application uses a master agent to control the game and uses messages between the two slave agents to transfer the game state.