Hello everyone.
Correct me if i'm wrong, but ...
Seems like the WebServer(Abyss) spawns a new process for each new request, unless a previuosly created one is idle. Even if a process is multithreading on the FCGX_ACCEPT_R procedure, only one thread is used.
Thought I could prevent the WebServer from spawning multiple
copies of a FastCGI App Server, but seems it is not possible. When you
try by exiting the new process, the WebServer responds with 500 Internal Server Error.
The objective is to have only one process centralizing all requests. So have to come up with another approach. A DLL using a Shared Memory Block(CreateFileMapping). So all copies of the FastCGI App load this dll, and a centralized processing now might be possible.
Thank you for your comments.
Correct me if i'm wrong, but ...
Seems like the WebServer(Abyss) spawns a new process for each new request, unless a previuosly created one is idle. Even if a process is multithreading on the FCGX_ACCEPT_R procedure, only one thread is used.
Thought I could prevent the WebServer from spawning multiple
copies of a FastCGI App Server, but seems it is not possible. When you
try by exiting the new process, the WebServer responds with 500 Internal Server Error.
The objective is to have only one process centralizing all requests. So have to come up with another approach. A DLL using a Shared Memory Block(CreateFileMapping). So all copies of the FastCGI App load this dll, and a centralized processing now might be possible.
Thank you for your comments.
Comment