To be honest I don't have a specific need... It's just that whenever I'm working in a non-aolserver environment (like fcgi or even mod_perl) I really miss the easy inter-thread communication, easy caching etc. So I thought I'd bring ruby to aolserver!
A smart idea that Vlad gave me is to use nsproxy as a base module, which apparently already fires up a pool of tcl interpreters in seperate processes. It might be a good model for our non-thread safe friends like Ruby and Perl. For starters I'm going to hone my ideas in a simple nsruby that uses a single ruby interpreter wrapped in a mutex lock to prevent reentry. If I like the result then I'll work on how to make it scale. On 5/22/06, Fred Cox <[EMAIL PROTECTED]> wrote:
Given this bit of news, you're probably better off helping the RoR/lighttpd/FastCGI projects. I'm curious to hear what you didn't like about this combination? Were you looking for intraprocess/interthread communication?
-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
