• Connect (a TCP connection is established)
• Client sends player name (a sequence of characters)
• Server sends number representing player color (0 == white, 1 == black)

• Server sends number representing turn (0 == white, 1 == black)
• If Player's turn
  • Player sends MOVE (see format below)
  • Server sends number representing response (0 == ok, 1 == illegal move)
• else
  • Server sends opponent MOVE

• Server sends number representing final winner (0 == white, 1 == black)
• Close (TCP connection is closed)

For the above protocol, a MOVE message is in the format of FROM:TO, where FROM and TO represent squares on the chess board. The rows of the chess board are numbered 1-8 and the columns a-h, like so:

As an option, the server could add a check if total time elapsed was too great. If so, the offending player would forfeit. A typical chess tournament allows about 2 minutes per move for the first 40 moves, and then 30 minutes for the rest of the game after. Note, this is not a requirement, just a suggestion. Options such as this, or others, could be specified when the server starts up via command line or a configuration file.

Links

The chess links from project 1.

Java Implementation

Here is some sample code showing a basic client and server in Java:

• Uses TCP: SocketServer.java, SocketClient.java

C++ Implementation, Windows

Here is some sample code showing system calls that you may find helpful for C++ code in Windows. Some must be used while others may be used depending upon your implementation:

• A simple header file to generate error messages for Winsock errors: sockerr.h

• Basic TCP sockets: tcp-talk.cpp, tcp-listen.cpp
• Basic UDP sockets: udp-talk.cpp, udp-listen.cpp
• Get the IP address of a host: getIPaddress.cpp

C++ Implementation, Linux

Here is some sample code showing system calls that you may find helpful for C++ code in Linux. Some must be used while others may be used depending upon your implementation:

• Basic TCP sockets: talk-tcp.c, listen-tcp.c
• Basic UDP sockets: talk-udp.c, listen-udp.c
• Setting a timer: setitimer.c
• Using POSIX threads: add2.c - add and subtract to a variable protected by a mutex (compile with -lpthread)
• Allowing multiple interrupts: select.c
• Parsing command line parameters: get-opt.c

Use the man command to find out additional information on the system calls used.

All assignments are to be submitted electronically via turnin by 11:59pm on the day the assignment is due. Turnin of code should include all the support files to allow your game to be built, along with detailed instructions on platform, libraries, etc.

The turnin should include a README with brief notes on how to run the server and client. It should detail any command line parameters for either. Also, notes on how a game against the AI is launched (as a separate client or on the server) should be included. Include information on where the system was successfully run.

The easiest way to submit your game is to zip the files, including the sub-directory. For ease of grading, call the sub-directory your_last_name-proj3 (ie- claypool-proj3), creating a proj3.zip file.

You will need to upload the file you are turning in to your CCC account on one of the CCC machines (ccc1 to ccc10). While logged into a CCC machine, you will need to enter the directory where these files are stored and execute the following:

  /cs/bin/turnin submit <course> <assignment> <file1> <file2> ...

where in our case, <course> is imgd4000, <assignment> is project2, and <file1>, etc. are the files to be turned in. So for example, you might enter:

  /cs/bin/turnin submit imgd4000 project3 proj3.zip

Following this, you should verify that your files have been entered into turnin by executing the following command:

  /cs/bin/turnin verify imgd4000 project3

Return to the 4000 Home Page

Send all project questions to the TA mailing list (imgd4000-ta at cs.wpi.edu).