A Multithreaded HTTP Server
There's one improvement that is customary in servers, and we will make it here. For all but the smallest of servers, it is usual to spawn a new thread to handle each request. This has three big advantages:
-
Foremost, it makes the server scalable. The server can accept new requests independent of its speed in handling them. (Of course, you need to run a server that has the mippage to keep up with requests.)
-
By handling each request in a new thread, clients do not have to wait for every request ahead of them to be served.
-
The program source can be better organized, as the server processing is written in a different class.
The following code demonstrates how we would modify our HTTP web server to a new thread ...
Get Just Java™ 2 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
