That was an experiment. However, in a production environment, it might not be a bad idea, as it would ensure that users experience a more uniform page access time. It would also help, under 5.2, to understand static memory utilization.
On Mon, Aug 9, 2010 at 10:15 PM, Dmitry Gusev <[email protected]> wrote: > Why pre-load pages? Isn't this hit startup time? > > On Tue, Aug 10, 2010 at 00:33, Howard Lewis Ship <[email protected]> wrote: > >> I was just experimenting with pre-loading Tapestry pages. It doesn't >> work, because if you inject an Asset, it looks for the >> Request.getContextPath() and hits a null (no Request object during >> startup). >> >> In Servlet 2.5 we could use the ServletContext.getContextPath() >> instead, which makes a lot more sense. >> >> At some point, we should require that 2.5 be the minimum. That's >> Tomcat 6 and up, and Jetty 7 and up and I think current versions of >> Geronimo. I wonder what app servers would be ruled out if we required >> 2.5? >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Dmitry Gusev > > AnjLab Team > http://anjlab.com > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
