Java project for HTTP-based mini game

1 Things to take into count ● The code structure ● Consideration of concurrency issues ● The design ● Choice of data structures ● Quality and use of unit tests 2 Description Write a HTTP-based mini game back-end in Java which registers game scores for different users and levels, with the capability to return high score lists per level. There shall also be a simple login system in place (without any authentication...). Deliver a zip file containing: ● The code in the src-folder ● A compiled version in a executable .jar file in the root folder ● An optional [login to view URL] or .pdf with thoughts and considerations around the program 3 Nonfunctional requirements ● This server will be handling a lot of simultaneous requests, so make good use of the availablememory and CPU, while not compromising readability or integrity of the data. ● Do not use any external frameworks, except for testing. For HTTP, use com.sun.net.httpserver.HttpServer. ● There is no need for persistence to disk, the application shall be able to run for any foreseeable future without crashing anyway. 4 Functional requirements The functions are described in detail below and the notation <value> means a call parameter value or a return value. All calls shall result in the HTTP status code 200, unless when something goes wrong, where anything but 200 must be returned. Numbers parameters and return values are sent in decimal ASCII representation as expected (ie no binary format). Users and levels are created “ad-hoc”, the first time they are referenced. 4.1 Login This function returns a session key in the form of a string (without spaces or “strange” characters) which shall be valid for use with the other functions for 10 minutes. The session keys should be “reasonably unique”. Request: GET /<userid>/login Response: <sessionkey> <userid> : 31 bit unsigned integer number <sessionkey> : A string representing session (valid for 10 minutes). Example: http://localhost:8081/4711/login --> UICSNDK 4.2 Post a user's score to a level This method can be called several times per user and level and does not return anything. Only requests with valid session keys shall be processed. Request: POST /<levelid>/score?sessionkey=<sessionkey> Request body: <score> Response: (nothing) <levelid> : 31 bit unsigned integer number <sessionkey> : A session key string retrieved from the login function. <score> : 31 bit unsigned integer numberExample: POST http://localhost:8081/2/score?sessionkey=UICSNDK (with the post body: 1500) 4.3 Get a high score list for a level Retrieves the high scores for a specific level. The result is a comma separated list in descending score order. Because of memory reasons no more than 15 scores are to be returned for each level. Only the highest score counts. ie: an user id can only appear at most once in the list. If a user hasn't submitted a score for the level, no score is present for that user. A request for a high score list of a level without any scores submitted shall be an empty string. Request: GET /<levelid>/highscorelist Response: CSV of <userid>=<score> <levelid> : 31 bit unsigned integer number <score> : 31 bit unsigned integer number <userid> : 31 bit unsigned integer number Example: http://localhost:8081/2/highscorelist - > 4711=1500,131=1220