Feature #825
closedsession management : dedicated process for each session : support for wthttpd
0%
Description
Currently session management using dedicated process for each session is only supported using FastCGI connector. Support should be added for the built-in server. FastCGI is dependent on the 3rd Party web servers, wthttpd support should be given priority.
Updated by Nilesh Chakraborty over 13 years ago
Forgot to login,
Was added by me.
Nilesh
Updated by Koen Deforche over 13 years ago
- Status changed from New to Feedback
Hey Niels,
For all our deployements, we tend to favour wthttpd too. But we haven't gotten around implementing the dedicated process mode, because that requires adding a reverse proxy implementation to the wthttpd.
I'm not sure it is high on our priority list either, since dedicated process mode is not that often used, and there is already (an albeit somewhat complex) a solid way of doing it using FastCGI.
Is this for you a blocking issue (given that you marked it as High priority) ?
Regards,
koen
Updated by Nilesh Chakraborty over 13 years ago
Hi Koen,
We're working on an application that would get benefit if the dedicated process mode is available (it's a server management program, and kernel-level isolation is preferred, since it'll make it more secure). Development will take 4/5 months, maybe more; it's not a blocking issue, we can begin work, but it would be necessary before we release the first version.
Do take your time, it's not an immediate necessity, will need it just before deployment.
Much appreciated.
Regards,
Nilesh
Updated by Koen Deforche almost 10 years ago
- Status changed from Feedback to Resolved
- Assignee set to Koen Deforche
- Target version set to 3.3.4
This is now availalable (same configuration as for fastcgi)
Updated by Koen Deforche almost 10 years ago
- Status changed from Resolved to Closed