Am Monday, 22. September 2003 23:48, schrieb Matt Sergeant: > On 22 Sep 2003, at 12:05, Jörg Walter wrote: > > I have a working, minimal intrusive and documented patch to add > > preloading of > > compiled XSP pages. > > Interesting. Is there no way to automate this better - such as > providing a path to XSP's you want pre-compiled, and then have them > compiled automatically at server startup? That would seem more sensible > to me. But maybe the design of XSP.pm isn't clean enough to support it?
Well, it would mean to duplicate a full AxKit environment at run time. ConfigReader, $r, possibly the cache including a correct key, loaded taglibs and everything - would be a bit of work, and error-prone, IMHO. The current way, you get an error message when a loaded module is missing - what you saw is exactly what you get. When parsing at startup time, you probably only notice a taglib was missing after you executed a code path using that missing taglib - and sometimes even that wouldn't be obvious. -- CU Joerg
