Distributed Guessing Game Project

Verified

Added on  2019/09/16

|1
|313
|161
Project
AI Summary
This project involves designing and implementing a distributed guessing game. The system comprises two clients, a middleware component, and two servers. Each server stores the number to be guessed and relevant data, displayed through labels or text boxes. Clients register to play, taking turns to guess. A protocol is needed to differentiate between registration and guesses. The middleware ensures data consistency between servers, which can communicate directly if online. Servers can simulate being offline (busy) without actually shutting down. A key aspect is handling potential data inconsistencies when servers have different availability. The grading criteria assess the functionality of the multi-client, middleware, and server components, the core guessing game mechanics, server on/offline toggling, and the handling of synchronization and game continuation.
Document Page
Stage Two:
There will be two clients, one middleware, and two servers.
Each server will hold the number to be guessed and any other relevant data – show via labels or text
boxes.
Once the two clients have registered to play, the game may commence – the clients will be expected
to play in turn. In order to differentiate between a registration and a guess some sort of protocol will
need to be devised - will be shown how to split a string in lecture notes.
Don’t forget that each transaction will expect a response back to the client.
The middleware will be responsible for maintaining consistency of data between the servers – the
servers will be permitted to talk to each other directly- but only if they are both on-line.
We will not actually turn a server off and make it off-line – we will assume that they will not fail –
just be busy (not available) sometimes i.e. can still send and receive messages, but that is all if off-
line –no game processing or interaction.
Complexity:
On each server will be a button on/off line. When the button is pressed it will toggle between
available and not available.
A transaction should be performed if at least one of the servers is active and up to date.
This type of system will offer the possibility of having inconsistent data and needs to be resolved.
Grading criteria
To accomplish stage two i.e. 2 multi-clients, middleware, 2 servers operational 45%-
55%
To get the basic operations of guessing game working 55-60%
To include some form of turning servers on/offline and maintaining game 60-65%
To consider and maintain synchronisation and the game continuation 65%>
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
[object Object]