If the index page is served from the cache 99% of the time (or more if it truly is static), why are you so concerned about pre-rendering it?
You should profile your application to determine the other areas where you should focus your energy on. On Nov 27, 5:36 pm, "Jeffrey L. Taylor" <r...@abluz.dyndns.org> wrote: > Oh, and rendering, i.e. generating the HTML, on the server side, not rendering > HTML in the browser. > > Jeffrey > > Quoting pepe <p...@betterrpg.com>: > > > That doesn't make any sense. How is the browser supposed to know what > > you are going to do before a request is made? > > > On Nov 25, 7:32 pm, "Jeffrey L. Taylor" <r...@abluz.dyndns.org> wrote: > > > Quoting Peter De Berdt <peter.de.be...@pandora.be>: > > > > > On 25 Nov 2009, at 23:39, Jeffrey L. Taylor wrote: > > > > > > I would like to pre-render some commonly accessed pages to speed up > > > > > response. > > > > > Is there any way to do this outside of a controller? > > > > > If you are talking about implementing caching, yes, you > > > > can:http://guides.rubyonrails.org/caching_with_rails.html > > > > Not quite, I am talking about rendering before the first request, so the > > > page > > > is already in the cache. Pre-emptive caching? Whatever. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
