server#

This method is the ‘main’ method of the server, it loops until it receives a keyboard interrupt, each loop searching for a request through the socket. Once a request is received, it will then create a thread that runs the handle method and pass the connection to the thread.

err_404#

This method returns a (header, response) tuple containing a basic error 404 response, for when the server can’t find a file in the file system, or the memo the user is trying to delete/put to doesn’t exist

err_403#

This method returns a (header, response) tuple containing a basic error 403 response, for when the user tries to make an API request without the valid credentials (a cookie called Session)

handle#

This method does multiple things

• It parses the incoming request, either sending it to one of the API helper functions, or grabbing a file from the file system and putting it into the response body
• It will also call helper functions such as check_header to add important details to the response header
• Lastly, it will concatenate the header and body of the response, send it to the client, and then close the socket

check_cookie#

This method checks a request for the existence of a cookie called ‘Session’. Should it find Session, it will return a tuple of (Cookie[“Session”], true), otherwise it returns ([Empty String], false)

check_header#

This method helps add the finishing touches to a response header, adding Content-Length, and any Cookies (setting a cookie if needed)

put_memo#

This method returns a (header, response) tuple, either header and response forming the header and body of a successful PUT response, or a 404/403 if the file isn’t found or the PUT request didn’t have any Session cookie

find_memo#

This method searches through all the memos in the file system to find one that matches the given ID, if it finds one it returns (True, [File path]), otherwise it returns (False, [Empty String])

delete_memo#

This method returns a (header, response) tuple, either header and response forming the header and body of a successful DELETE response, or a 404/403 if the file isn’t found or the DELETE request didn’t have any Session cookie

extract_body#

This method takes the raw data from a request and separates the header from the body, either by spliting on ‘/r/n/r/n’ or ‘/n/n’, depending on which is valid.

post_memo#

This method returns a (header, response) tuple, with the header being a 200 OK header, and response being empty, showing that it successfully created a new memo on the server. Provided the method didn’t run into conditions that would lead to a 403 Error.

get_all#

This method returns a (header, response) tuple, with the header being a 200 OK header, and response being the body of the response, which is a list of JSON memo objects