I have lost about three days checking the Wt source code trying to figure out what kind of risks there could be if I would choose a dynamic FastCGI deployment for my Wt site, because there is nearly no documentation about that, and I'm not sure about anything.
My web server is an Apache 2.4.7. I'll try to sumarize my doubts with the following questions/sentences: Suppose that I deploy my website as a dynamic FastCGI aplication under dedicated process mode, with a maximum number of 100 sessions, and after X days of working, Apache has created 5 instances of the same process (5 Wt main processes): - Do I have a maximum of 500 sessions? (100 sessions per main process). Because each fcgi/Server instance has its own `sessions_` object. - If the first Wt process created by Apache, launchs an auxiliary process to manage the sessionId 4 (for example), and another HTTP requests arrive for the same session, Apache sends that HTTP request to a process of his choice, so, the HTTP request for the sessionId 4 could be delivered to a Wt process which didn't create the corresponding session process. How is managed that? As far as I know after reading the source code, both main processes will be connected to the same session socket, and I don't know if that is the expected behaviour. I mean, should I use dedicated process mode for dynamic FastCGI applications? About the second point, if the deployment strategy were SharedProcessMode instead of Dedicated, the question would be very similar, because everything is about having different Wt process which knows nothing about the other ones. So, what approach is safer?
------------------------------------------------------------------------------
_______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
