https://github.com/stvhwrd/SENG-468-HTTP-Server/blob/666cd64f986df75d0320420d175af8f18cd8637d/main.go#L87

"This should be handled by commonlib. The workload generator already composes the messages correctly, so all you need to do is have a switch to handle the message type and go from there. See transaction server for reference."

Produce Log Files

In addition to the client activities, DayTrading requires full auditing capabilities; hence, complete transaction logs must be able to be produced on demand that detail of all client activities in the
system (including timestamps of all transactions), a record of each individual transaction, each transaction’s processing time information, and all account state changes within the system. This log must be dumped from the system as an ASCII text file when it receives the DUMPLOG command.

Constraints

• Format: XML
• Schema: this schema

(:point_up: Log files not of this exact schema will not be accepted)

Validation

Log files can be validated using xmllint against the provided XSD file

xmllint --schema logfile.xsd --noout OURLOGFILE.xml

Example

https://www.ece.uvic.ca/~seng468/ProjectWebSite/ExampleLog.html

HTTP Server will contribute four logs:

• DebugType
• ErrorEventType
• SystemEventType
• UserCommandType

DebugType

Debugging messages contain all the information of user commands, in
addition to an optional debug message

• "timestamp": int // UNIX timestamp
• "server": string // name of server eg. "Transaction Server"
• "transactionNum": int // enumeration of transaction
• "command": string // one of the known commands ("BUY", "SELL" etc)
• "username": string // optional alphanumeric username
• "stockSymbol": string // optional three-char alphanumeric stock symbol ("NWC", "BTK")
• "filename": string // optional name of file to be written to
• "funds": decimal // optional dollars and cents (eg 24.99)
• "debugMessage": string // optional debug message or description

ErrorEventType

Error messages contain all the information of user commands, in
addition to an optional error message

• "timestamp": int // UNIX timestamp
• "server": string // name of server eg. "Transaction Server"
• "transactionNum": int // enumeration of transaction
• "command": string // one of the known commands ("BUY", "SELL" etc)
• "username": string // optional alphanumeric username
• "stockSymbol": string // optional three-char alphanumeric stock symbol ("NWC", "BTK")
• "filename": string // optional name of file to be written to
• "funds": decimal // optional dollars and cents (eg 24.99)
• "errorMessage": string // optional error message or description

SystemEventType

System events can be current user commands, interserver communications,
or the execution of previously set triggers

• "timestamp": int // UNIX timestamp
• "server": string // name of server eg. "Transaction Server"
• "transactionNum": int // enumeration of transaction
• "command": string // one of the known commands ("BUY", "SELL" etc)
• "username": string // optional alphanumeric username
• "stockSymbol": string // optional three-char alphanumeric stock symbol ("NWC", "BTK")
• "filename": string // optional name of file to be written to
• "funds": decimal // optional dollars and cents (eg 24.99)

UserCommandType

User commands come from the user command files or from manual entries
in UI web forms

• "timestamp": int // UNIX timestamp
• "server": string // name of server eg. "Transaction Server"
• "transactionNum": int // enumeration of transaction
• "command": string // one of the known commands ("BUY", "SELL" etc)
• "username": string // optional alphanumeric username
• "stockSymbol": string // optional three-char alphanumeric stock symbol ("NWC", "BTK")
• "filename": string // optional name of file to be written to
• "funds": decimal // optional dollars and cents (eg 24.99)

Doesn't appear to be a downstream error. First command goes through but the second will return EOF to the workload_gen and the running thread on the server will crash.

If no connection exists on eg. port 81 and HTTP Server tries to send a message to that port then it panics and crashes

Transaction number is set to 0 when server starts up. If it crashes and restarts, it would start at 0 again.
It should instead continue from most recent transaction number.

Display Summary via Web Client

Purpose: A summary of the given user's transaction history and the current status of their accounts as well as any set buy or sell triggers and their parameters is displayed to the user.

Data Fields

Data will be transferred to Web Client as JSON and rendered by Web Client.

JSON Schema [WIP]

{
    "userSummary":
    {
        "account":
        {
            "userid": "",  // Globally-unique identifier
            "dollarsAvailable": "", // Current buying power
            "dollarsPending": "" // Amount on hold
        },
        "transactions": [
        {
            "timestamp": "", // Timestamp of execution
            "id": "",  // Globally-unique transaction identifier of
            "type": "", // Type of transaction eg. BUY, SELL
            "status": "", // Status of transaction eg. pending, complete, cancelled
            "dollarsAmount": "", // Dollar amount involved in transaction
            "sharePrice": "", // Price per share at time of purchase
        }],
        "holdings": [
        {
            "stockSymbol": "", // Unique identifier
            "shares": "",  // Number of shares purchased
            "sharePrice": "", // Price per share at time of purchase
            "purchaseDate": "" // Timestamp of execution
        }],
        "triggers": [
        {
            "type": "", // Type of trigger, eg. BUY, SELL
            "dollarAmount": "",  // Dollar amount involved in transaction if triggered
            "transactionId": "" // Globally-unique trigger identifier
        }]
    }
}