> The problem with this approach is that the “init” can take a couple seconds > with all the bits I’m loading in, which means the first person to hit a new > interp is getting a really crappy experience. I would prefer to do all the > init on startup of the child and interp so that the child isn’t really even > ready to serve requests unless it has already gone through my init. > > I’m not ENTIRELY sure what I’ve just said is relevant to this conversation. > If not, pleas excuse me and just consider them the ramblings of an old man. :)
+1 on both points :-) Well, meaning I am not sure whether it's relevant, technically, but it's an important point for many people. -- David N. Welton http://www.dedasys.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
