Concepts of Concurrent Compuation – Project

As a new employee at the Algonquin web-server company, you have been tasked with developing a new experimental web-server. You, being on the cutting edge of software development, have decided to implement this system in SCOOP. This will allow you to make your employer aware of the newest developments in programming languages, and how they may help the company. 2 Requirements You must implement a web-server that handles a very small subset of the HTTP/1.1 protocol, a full description of which is available in the W3C RFC-2616 [2]. The server must be concurrent, i.e., able to serve more than one request at the same time. Additionally, for record-keeping purposes, the server must be able to record the each client’s IP address along with the requested files in a mutable data-structure shared among processors. Since this is a proof of concept, you are only required to handle GET requests for relative URIs (i.e., no “* ” requests). As a minimum standard, the server must be able to handle requests from at least two of the major browsers: Internet Explorer, Firefox, Chrome, Safari, Opera. Please remember that not all requests may be small HTML files. Additionally, the server must respect the Connection header of the request and keep the connection alive for future requests if asked to. This aspect differs from the wording in RFC 2616, which allows a server to immediately close a keep-alive connection if it wishes. If asked to close the connection, then the connection should be closed. More details on connections can be found in RFC 2616, Section 8. File preferences (via Accept) do not need to be strictly adhered to, any of the acceptable files may be served. You may assume that the identity content encoding is always acceptable. Accept-Languages may be ignored entirely. All other request headers can be ignored, as long as they do not contradict the above requirements.