A WWW server interprets the HTTP protocol while responding to clients' requests.
-
Currently, every time a new client connects to a server, the server "forks" itself, creating a new copy of the server which now handles the established connection exclusively. Forking a new process is an expensive operation. In addition memory and other system resources are being wasted.
-
An alternative solution is to have a multithreaded server, which will create a new thread each time a new connection is requested. This is not only more efficient if terms of performance and memory consumption, but allows to implement easily interactions between different client. Something, which is a natural next step in the Web technologies.
|