12.09.2015 3:16, Massimo Manghi пишет:
Then why did it stop working the way it worked with Tcl 8.5? I think
this is the question to be answered.
As far as I know, Itcl3 does lazy object creation, i.e. it only creates
object stub command instead of real object at first. This stub creates
real object later when and *if* it is needed. I think Itcl4 could stop
doing so. I think I can restore similar behaviour in my app on my own
where it's hardly needed.
As a possible workaround I'm looking for a way to pre-load my sources
before actual request comes now..
This is the way ChildInitScript works now, it runs before requests come
in, why didn't it work for you?
It works. Just wasn't used before.
I reworked the app to allow code loading in ChildInitScript. It's OK.
Apache restart takes rather long time, however.
Pre-loading app code in ChildInitScript has it's drawbacks.
During development, code with errors gives error messages repeated for
every worker process.
When there are several apps pre-loaded, starting extra worker processes
due to some request storm for *single* app causes loading of *several
apps* into *every extra worker* instead of loading just one app into them.
I've done also some experiments to load app code in ServerInitScript.
Stumbled upon strange errors. Abandoned this.
We have also the GlobalInitScript
(actually only when separate virtual interpreters are disabled)
Is there any difference between GlobalInitScript and ChildInitScript
defined outside any of VirtualHost's?
--
Best regards, Anton.
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
