|
From: Nathan D. <na...@ch...> - 2002-09-12 17:36:27
|
> > Yes, makes good sense. As far as formats for the config file. Hmm. Are > there any obvious logical lines that you could draw through the config > parameters? Actually, what are the other config parameters? Hmm. At the moment I am certain of two: defaultPersister rootModusDirectory (/WEB-INF/Modus/) I could also see a list of object types to preload into the cache when Modus initializes. If Modus expands to include things like page rendering, security, etc. I could see many things related to those issues as well. You can probably see now why I haven't yet put a config file together -- the whole thing needs a little more time to "bake" before it's clear what belongs where. Along with the config, I think there would be a modusInit.cfm that could be called as a custom tag in the Application.cfm of an app using Modus -- it would make sure the rootModusDirectory was created, would initialize the cache, the formFieldFactory, and anything else that should be in the server.modus scope. |