haryle / java_server Goto Github PK

Need to

• Parse text file into json
• Parse string message into json

• 1st PUT Message is 201 CREATED
• Subsequent messages is 200 with data bodies
• PUT message items is stored in a map

When each text file contain data from other regions/same region but different timestamps

Generate HTTP Request using builder structure

Parse HTTP Request received from String Message

Generate HTTP Response using builder pattern

Parse HTTP Response from String Message

Write tests for both cases

Request HTTP Request parser

• Write Github Action workflow
• Write compilation and testing make targets
• Add README file

• Read server URLs like GET server.
• Read the location of a file in the local file system.
• Assemble to JSON:
  • No ID means error
• Receives response from the Agg Server and compares results

Implement a Java communication channel that allows for

• Message delay
• Message drop
• Message arrives out of order

Update based on datetime latest

Add Request handle thread

• Handle GET request - ID exists
• Handle GET request - empty
• Handle GET request - ID does not exist

• Client to wait k amount seconds before resending message. Implements using exponential backoff
• Client to retry for a maximum of m times

Starting server

• Check if Backup file is present. If it is, restore from backup.

When running

• Save backup to local every x amounts of seconds.
• Run as background task.

Client can connect to server single threaded design

At the very least:

• Map<String, String> where key is the content server ID, and value is the content
• Map<String, String> where key is the station ID and value is the weather data content
• List containing the requests

• Parse server info (servername, port) from URL:
  • http://servername.domain.domain:portnumber
  • http://servername:portnumber
  • servername:portnumber
• Get station ID:
  • Request all information if no station ID is provided
• Create GET message
• Receives response and displays to stdout the Body of response.

• Send data to Aggregation Server
• Content is visible to GETClient

• AggServer spawns a connection.
• Connection read message and allocate Timestamp.
• Connection decides whethr the message can be handled locally - i.e. empty GET or must be sent to message queue
• If cannot be handled locally, send the task to message queue

Use bashscripts to test

• One Client
• Multiple Clients