On Feb 14, 2007, at 2:33 AM, Paul Querna wrote:
- Promote and include a external-process communication method in the
core. This could be used to communicate with PHP, a JVM, Ruby or many
other things that do not wish to be run inside a highly-threaded and
async core. The place for large dynamic languages is not in the core
'data router' process. Choices include AJP, FastCGI, or just HTTP. We
should optionally include a process management framework, to spawn
these
as needed, to make configuration for server administrators easier.
This makes a lot of sense, but please NOT AJP... It
seems to be that staying with HTTP is the most scalable,
easiest to debug and troubleshoot, and the most straightforward.
I agree that we need to improve our FastCGI capability as well.
