Re: [AOLSERVER] interpreter lifecycle

2005-05-28 Thread Jim Davidson
In a message dated 5/28/05 11:37:23 AM, [EMAIL PROTECTED] writes: 3. Use the package interface along with ns_ictl to manage state clearly, e.g., replace the confusing code in bin/init.tcl with the following and expect folks to own this config for their own install as they do with nsd.tcl: ns_ic

Re: [AOLSERVER] interpreter lifecycle

2005-05-28 Thread Tom Jackson
On Saturday 28 May 2005 08:14, Jim Davidson wrote: > 5. Finally, the last thing we should consider is giving up on virtual > servers. It turns out that there is still quite a bit of code complexity > to support virtual servers and more importantly it confuses the "process" > init with "server"

Re: [AOLSERVER] interpreter lifecycle

2005-05-28 Thread Jim Davidson
Howdy, I've been following this thread the last few days -- great discussion.  Let me add a few points and suggest how we can move forward. First, I'm responsible for the current approach of initializing Tcl interps in AOLserver and I agree with Zoran -- it's clumsy.  Aside from failure on my

Re: [AOLSERVER] interpreter lifecycle

2005-05-28 Thread Zoran Vasiljevic
Am 27.05.2005 um 00:47 schrieb Jeff Hobbs: This I will disagree with. If you can handle it all in C, I think you will save time. A lot will be in the copying itself, but saving any and all parsing is a bonus. Hmmm...since the scripts will have to jump interp/thread, they need to be re-parse