Hmm, might be worth trying that until ruby gets more thread friendly. I have the code from Jim Lynch's attempt at nsperl as a start.
On 5/23/06, 'Jesus' Jeff Rogers <[EMAIL PROTECTED]> wrote:
Mark Aufflick wrote: > 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. Perl can be thread-safe, if you jump through the right hoops (-DMULTIPLICITY and maybe another define). I did some work on making the tclperl package thread-safe with the main intent of making it work in aolserver, and got pretty good results. If there was a DBD interface to the Ns_Db functions that would make aolserver a *schweet* environment for perl apps since there is no database pooling on apache. -J -- 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.
-- Mark Aufflick e: [EMAIL PROTECTED] w: mark.aufflick.com p: +61 438 700 647 f: +61 2 9436 4737 -- 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.
