Project: A Multithreaded Server
Overview -
In this assignment, you will learn how to implement a multi-thread server with a thread pool. To get started, download a copy of the starting source code from blackboard course assignment link. The goals of this assignment are as follows:
- To gain experience in writing and debugging multi-threaded code. In particular, you will be exposed to code that can deadlock or have race conditions.
- To make use of common synchronization primitives such as locks and condition variables.
- To gain some tangential exposure to network programming.
- To understand the concept of overlapping I/0 and computation.
Background -
As I'm sure you know, the Internet has exploded in popularity over the past decade. Driving much of this explosion is the proliferation of networked servers, which are programs that run "in the guts" of the Internet. Client programs (such as web browsers) communicate with these servers over the network, sending requests and reading back the servers' responses. For example, a web browser will send a web server a request for a particular web page; the server will process this request, and then respond by sending back the page's HTML, which the web browser reads, parses, and displays. One of the challenges in building Internet services is dealing with concurrency. In particular, many independent clients can simultaneously send requests to a given server. A server therefore must be designed to deal with concurrent requests. There are many different strategies for doing this; we will explore two in this project.
Deliverables -
You should submit a write-up of what you did (name it readrae.txt), plus all the source code files for your project. Your write-up should include the following:
- A verbal description of the structure of your thread pool implementation, including a list of any design decisions you made.
- A list of critical sections inside your thread pool code (and why they are critical sections).
- A description of the synchronization inside your thread pool. What condition variables did you need, where, and why? Under what conditions do threads block, and which thread is responsible for waking up a blocked thread?
Submit in the all your files as a gzip compressed tarball. Include in the tarball all files necessary for a successful build! The name of your attachment should be project.tar.gz.
Your submission will be graded by compiling and running it and reviewing the source code.
- As usual, the grading platform is linprog. Make sure your code works on linprog.
- Please make sure your source code can compile. Absolutely no credit if it does not compile.
- Get rid of warnings from the compiler. Points will be deducted if your code has excessive warnings.
- Please don't include the binary files. Do a make clean before submission. You'll make grading harder for us if you do.
- Please don't leave out any files! You'll make grading harder for us if you do.
- Please don't modify any files you don't need to! You'll make grading harder for us if you do.
- Please don't send us the meta-information from your revision control system! You'll make grading harder for us.
And if we have a hard time grading, you'll have a hard time getting points!
Attachment:- Assignment Files.rar