Jon Stevens wrote:
>
> on 7/12/2000 11:21 AM, "Steve Ruby" <[EMAIL PROTECTED]> wrote:
>
> > making module.cache=true in TurbineResources takes the time
> > for all handleRequests from about 2+ seconds to 1 or just under
> > on average, so it makes a BIG difference but it isn't the whole problem,
> > thanks..
>
> Ok, is your screen doing a lot of static initializations or something?
> -jon
No, nothing extreme, a two String[] are setup in the main screen.
the problem Seems to be in what John McNally pointed out.
With module.cache=false, if I #parse my navigations
in my layout then I go from 2400ms to do handleRequests to 300ms
and then down to blazin' fast if I go to module.cache=true.
The more $navigation.setTemplate() lines I add to my layout
the slower it gets to the tune of about 1 second per
call (this is only in hte handleRequest calls) doBuildTemplate
for the screen I'm testing this with is very fast.
The problem with #parse'ing my navigations in is how do I put
stuff in their context? with $navigation.setTemplate() my screen
can set stuff in the context of the layout.
I have a feeling my implementation may be a bit off..
Only screens should run the matching named screen Class
correct? Just out of curiosity why can't layouts, and navigations
also run <packagename>/layout/layouttemplate.class files?
What is the proper way for adding values to the context of
the navigations?
Thanks again.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
