Hi, That is an interesting idea. Maybe you can make a proposal in a ticket for Fabien to look at?
- Jon On Tue, Jun 29, 2010 at 12:49 PM, Jordi Boggiano <[email protected]> wrote: > Heya, > > I do realize this is most likely not trivial and maybe almost impossible > due to the structure of the request/response model that waits for a full > response to be there before it sends it. > > However, I can't help but suggest that it would be great if you could, > in the templates, call flush() (or rather a wrapped version of it I > guess) to force the output to start and some stuff to be already sent to > the client. > > Typically this means if you can flush after the <head> is done, that the > user's browser can already start downloading css files or do other stuff > while the rest of the page is being rendered and then sent. > > This wouldn't change anything in the benchmarks obviously, but it might > mean much faster render times for end user, which matter a lot. > > Cheers > > -- > Jordi Boggiano > @seldaek :: http://seld.be/ > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- Jonathan H. Wage http://www.twitter.com/jwage -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
