From: Vlad S. <vl...@cr...> - 2006-07-13 20:00:41
|
This is from file.tcl, # And here's the magic part. We're using "for" here to translate the # text source file into bytecode, which will be associated with the # Tcl_Obj we just cached (as its internal representation). "eval" # doesn't do this as the eval provided in Tcl uses the TCL_EVAL_DIRECT # flag, and hence interprets the text directly. # uplevel [for [lindex $pair 1] {0} {} {}] Stephen Deasey wrote: > On 7/13/06, Vlad Seryakov <vl...@cr...> wrote: >> I meant .tcl file cacheing, which is in tcl/file.tcl when >> enabletclpages=on then all requests to .tcl are cached in global cache. > > Right, the Tcl is read from disk and cached in memory. But only the > Tcl *source*. It needs to be byte code compiled before use. This is > what Andrew is talking about. > > Our cache stringifys everything that goes into it -- you can't share > Tcl objects between threads. Therefore, every time you retrieve the > Tcl page from cache (not disk), you still have to byte code compile > it. > > aolserver3.x-ad13 cached the byte code per-interp. > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |