Since we are not allowed to use pthread and and we can fork new processes only for CGI it is clear that the architecture of our 'webserv' web server will be event driven.
There are basically three possible architecture models to handle concurrent requests in a webserver:
- multi thread, like Apache Tomcat
- multi-process, like Apache in Prefork MPM (Apace supports multiple architectures)
- event-driven, like NGINX
The most famous single threaded piece of software is node.js, which relies on the Google V8 Engine, which powers also Google Chrome.
The note as in the title of the issue, could be a short sentence in the README, if we want to create more content about it, then the note coud be integrated in an ad hoc document.
This is explicitly left as 'backlog' issue.
Since we are not allowed to use pthread and and we can fork new processes only for CGI it is clear that the architecture of our 'webserv' web server will be event driven.
There are basically three possible architecture models to handle concurrent requests in a webserver:
The most famous single threaded piece of software is node.js, which relies on the Google V8 Engine, which powers also Google Chrome.
The note as in the title of the issue, could be a short sentence in the README, if we want to create more content about it, then the note coud be integrated in an ad hoc document.
This is explicitly left as 'backlog' issue.