- Implement a simple HTTP client, which gets the default www-page from the test TCP server of Tools and prints the page on screen (on the console window, no GUI reguired for any excercise).
- (a) Implement a TCP server that echos back what client sends and adds the server's name in front of the echoed text separated by a ; -character. Below some examples. (b) Also implement a client that that sends a text string to the server and receives the response so that it can separate the server name and the echoed text based on the ; -character and prints them on screen e.g. as below.
- Implement simple SMTP client, that can communicate with the test SMTP server using HELO and QUIT commands
- Implement MAIL FROM, RCPT TO sekä DATA commands to the simple SMTP client.
SMTP Server state machine SMTPServer.svg. An example state machine for client can be found from the videos page.
- Implement an UDP server that sends a message from a client to all other clients that have already send a message to the server. Message format is Sender name;chat text
- Implement a client that can send at least a single message to the server and then receive several messages from the server and prints on screen the sender and the text separated by : -character e.g. Ari: Hello!
Implement
The client state machine
- Client JOIN state
- Client GAME state
- Protocol frame structure
- The frame has two fields: |message|value|
- Fields are separated by a space or ; -character
- Protocol messages: JOIN, DATA, ACK, QUIT
- JOIN - join the game - value = Player name
- DATA - data related to the game - value = the number quessed (in this game, same message used to deliver Client->Server and Server-Client DATA messages)
- ACK - each message is ACKed - value = status code informs of success etc. (after status code there might be text (separated by a space), this text which can contain spaces is part of the value -field)
- QUIT - game ends - value = 501 (you win) or 502 (you lose)
- Examples of ACK-message status codes that can be used (example server might have others too)
- 201 JOIN ok, waiting for second player
- 202 [opponent name], 2 players joined, you can start
- 203 [opponent name], 2 players joined, your opponent can start
- 300 DATA OK, Acknowledgement of correctly received data
- 4xx error messages (you should implement at least one)
- 400 undefined error
- 401 JOIN not possible (i.e. already 2 players playing)
- 402 Not your turn
- 403 errorneous ACK message
- 404 wrong frame format
- 407 the quess was not a number
- 500 QUIT OK, send in response to a QUIT message
Implement
The Server State machine
Hints
- the server WAIT and END states.
- rest of the server states
- The logical function of the server (keep track of who's turn it is to quess) and several error messages.
Last updated 10.3.2016
Back