You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Holger Pretzsch (JIRA)" <ji...@apache.org> on 2011/05/06 13:24:03 UTC

[jira] [Commented] (TAP5-294) Add easy way to pre-load pages at application startup

    [ https://issues.apache.org/jira/browse/TAP5-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029892#comment-13029892 ] 

Holger Pretzsch commented on TAP5-294:
--------------------------------------

I implemented this myself in an earlier version by using the PagePool service and checking out and releasing the pages I wanted to pre-load, which improved first request times noticably. However, when I upgraded from 5.1.0.5 to 5.2.4, this simple implementation broke and I'm now running into various issues while trying to fix it.

It would be very helpful if this were included as a standard feature.

> Add easy way to pre-load pages at application startup
> -----------------------------------------------------
>
>                 Key: TAP5-294
>                 URL: https://issues.apache.org/jira/browse/TAP5-294
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> It would be nice if there was an easy way to have Tapestry pre-load some or all pages at application startup time. This would make startup time longer, but would make the first serviced request operate more quickly.  It would be good if this could be limited to production mode.
> I think this would be just a matter of iterating through the list of available pages and asking for an instance of each one.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira