I intend to deploy JACL in a server-side process whereby clients make
server requests that TCL code be run on their behalf. Each client's
request will run in a JACL interpreter.
I was thinking of reducing overhead by creating a pool of shared
interpreters rather than instantiating one for each new client request.
However, each request may cause the creation global variables, procs,
etc which should not be in place when the next client request comes
along.
So if I am to use a pool, I need to be able to "clean-up" the
interpreter when it is returned to the pool. I could do this by
interating over the lists returned by [info globals], [info procs],
[info loaded], etc and perform tcl code to unset variable, clear
procedures, and forget packages, etc.
However, I wonder if:
(1) I can really do a complete "clean-up" this way,
(2) If this approach is faster than simply instantiating new
interpreters as needed and killing them off when done,
(3) If there is some built-in method that can be called to do this.
Any thoughts/hints are appreciated.
Thanks,
David P. White
HMS Software
----------------------------------------------------------------
The TclJava mailing list is sponsored by WebNet Technologies.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
A list archive is at: http://www.findmail.com/listsaver/tcldallas/
