On 2006.08.25, Rusty Brooks <[EMAIL PROTECTED]> wrote: > So it looks like the nsproxy establishes a tcl interp that is persistent > between connections, and can be accessed (well, code can be sent to it, > results can be sent back) by any thread? Perfect!
Yup. It's useful in solving many kinds of problems. > Just out of curiosity, what problem was nsproxy explicitly created to > solve? Just generic tidbits like this, or was there another force > behind it? Primarily, it's useful for executing Tcl "exec" and other non-threadsafe code, since it runs in its own process space external to the main nsd process. It's also a good place to run code that's not well-behaved, because you can then kill off the proxy child process ... as opposed to executing it within the main nsd, nad having a run-away thread that you can't stop without bouncing the whole server process. -- Dossy -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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.
