https://github.com/dekz/dc

Distributed Communication - Cricket Information
https://github.com/dekz/dc

Last synced: 25 days ago
JSON representation

Distributed Communication - Cricket Information

• Host: GitHub
• URL: https://github.com/dekz/dc
• Owner: dekz
• Created: 2009-09-19T13:28:35.000Z (over 15 years ago)
• Default Branch: master
• Last Pushed: 2009-10-23T10:59:16.000Z (about 15 years ago)
• Last Synced: 2024-04-17T02:56:42.316Z (9 months ago)
• Language: C
• Homepage:
• Size: 211 KB
• Stars: 3
• Watchers: 4
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README

Awesome Lists containing this project

README

        
TASK 1 - up to 74% (74%)

This task is to develop a client/server system for cricket funs to query the statistics about the bating figures for a cricket test between Australia and West Indies. The statistics about the test are stored in a text file, batting.txt, which should be stored in the server. The information stored in the text file includes Players’ Name, Country, Innings, Total Runs, Times Not Out, Highest Score, and Highest Score Was Not Out. 

A user can use the client program to query about the information about a player. When a user enters a player’s name, the client program sends a request to the server and the server retrieves the information about the player and sends it back to the client program. The information about the player is then displayed on the client’s console. 

TASK 2 - up to 84% (10%)

This task is to extend the server program so that it records and displays the total number of the queries about a player on the server side every time a query about the player is received by the server. 

TASK 3 - up to 100% (16%)

This task is to add authentication to the client/server system. When the server receives a request from a client, the server needs to check if the client has been granted the access to the cricket test information by verifying the user’s username and password. If the user name entered by the user is found in an authentication file, authentication.txt, and the password entered by the user matches the corresponding password in the authorisation file, the server grants the access to the client and the user can query about the information about the players; otherwise, the server sends a message to the client indicating the user does not have the access to the system and then terminates the connection between the server and the client.

To keep the task simple, you may assume that the authentication file has been created and it is managed manually, and that all the users that have been granted access to the system have been saved in the authentication file.

USERNAME 	PASSWORD

dekz		123456

Bjeans		999999