Absolutely. In my testing, it has been the most stable and flexible for
my uses: I’m not writing a single script system, so mod_ruby’s
namespacing issues are painful. I don’t want scripts owned by different
users, in different parts of the system to clash.
Privilege separation is important – FCGI allows scripts to run under
different userids than the webserver. That’s a plus.
No need for separate apache instances for different configurations.
Now, on top of that, WEBrick is a standard part of the distribution now,
so I imagine many interesting things will be released as servlets only
– compatibility with that is a must, but I’m stuck with Apache for
other parts of my site, and mod_proxy seems a brittle solution.
All this led me to create the module, so I can use webrick servlets
On Sat, Feb 14, 2004 at 06:55:03PM +0900, MikkelFJ wrote:
“Aredridel” firstname.lastname@example.org skrev i en meddelelse
I’ve been working this week on a webrick servlet compatible module using
FCGI. I prefer Apache as a general webserver, the process separation of
CGI and FastCGI over mod_ruby, and the webrick API – so I combined
I’d appreciate comments, suggestions, improvements, and certainly not
least, success stories.
I think FastCGI is the way to go.