Andrew Piskorski wrote:
On Tue, May 24, 2005 at 02:10:33PM +0100, Stuart Children wrote:
in a thread between connections. So the interpreter is *not* re-cloned
between requests. Indeed, testing a template that increments a namespace
Most definitely not. AFAIK it never has been, ever, in any version of
AOLserver.
OK. It was "Each connection thread that requires Tcl will create a copy
of the original interpreter." on
http://www.aolserver.com/docs/devel/tcl/tcl-general.html that set me on
the wrong initial track - but I realise now that "connection thread"
actually serves many "requests".
I don't think ANYONE prefers the current design; it is a compromise
due to performance and implemention constraints. Jeff Hobbs has
pointed out that those implemention constraints should now be fixable,
it's just a matter of doing the work.
Right.
I'd be willing to help coding on this, though my knowledge of TCL
internals (from a C POV) is currently a bit lacking. Although to be
honest I'm probably looking for a quicker solution than that seems to
Just what IS the immediate problem you're trying to solve? I don't
think you've ever actually said.
Well, there's not a specific issue. I've got a bunch of "legacy" TCL
code that I want to run under AOLserver. At the moment I'm just trying
to understand how AOLserver works to ensure I set things up in the
appropriate manner and I'm aware of what issues may arise.
For example, much of the code makes use of namespaces, but it's
previously been run in an environment where each execution gets its own
interpreter. I now know that potential assumptions in my code about
initial state may not be safe under AOLserver. There's sufficient code
that going through it all to check this is not a trivial task. (If
globals weren't cleared out either I'd have a nightmare. :])
I'm also simply interested to understand for my own benefit, and so I
can develop future code in a manner that best suits AOLserver.
Would people would be interested in a seperate "first adp error aborts
the whole file" feature for 4.[01]? From a brief inspection of the
No, I'm not interested, but I believe that feature already exists, Jim
D. implemented it - or so I seem to recall; I could be wrong.
I'll dig further with the CVS sources...
Thanks
--
Stuart Children
--
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.
