Bas Scheffers wrote:
Zoran Vasiljevic said:
First, I doubt that the process will be fast enough when applied to
tons of loaded procedures, namespaces, variables and all of those things
My thought exactly. Nice for new interpreter creating, but not for
per-request use.
If the interpreter cloning were made viable, then you could easily make
this configurable in the same manner that interpreter lifetime is now
(though my researching has unearthed comments that connsperthread != 0
may not currently be safe?). Then people would be free to choose between
having a "known starting state" interpreter but a potential performance
hit, vs dealing with namespaces persisting.
I don't see how the current AOLserver way of dealing with this can be
improved, I find it works well and is very intuitive.
It certainly seems to work if your code is written with it in mind, and
now I know what's going on I can deal with it. So there's just a
documentation issue which is certainly easy to fix! And I intend to.
--
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.
