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? --- Jeremy Henty <[EMAIL PROTECTED]> wrote: > On Monday, May 22, 2006 7:26 am, Mark Aufflick > <[EMAIL PROTECTED]> wrote: > >An issue I have become aware of is that the ruby > code is entirely non > >thread safe. > > > >That's a real bummer. I'm thinking that possibly I > could make a pool > >of interpreters and supervise access to them. > > Is that even possible? I think the Ruby interpreter > lives in C global > variables (blech!) so it may not be possible to have > more than one per > process. I don't have it to hand but IIRC > "Programming Ruby" admits > that Ruby was never designed to be embeddable. > > Regards, > > Jeremy Henty > > > -- > 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. > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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.
