Andrew Piskorski said: > I suspect that re-initializing a Tcl interpreter to a known state > probably isn't nearly as impossible to do efficiently as you seem to > think. (Which is kind of interesting, so perhaps some guru will > comment further.) Well, then why doesn't any Tcl based web app product do it? (AOLserver, Vignette, mod_tcl) Remember that anything more than a few milliseconds is too slow. If your app is currently able to handle 20 requests a second, something that takes 50ms extra to do, halves that number.
> Safe-Tcl or something like it might be relevent there. Could work and be quite fast. Create all user procs in one master. (rewriting the procedure name) On each request, create a safe interp with aliasses to only that user's procs and execute as that user's UID. Not too familiar with Safe-tcl, though. But t does require some re-engineering, basicaly making Tcl multi-user, which is what I suggested needed to be done in an earlier post to make safe and fast multi-user hosting possible. > Basically, you're making a lot of awfully sweeping software design and > performance assertions here. I wouldn't be that surprised if you Gotta start somewhere! ;-) Would love to hear from the guys that actualy code the guts of AOLserver. Bas. -- 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.
