It seems that output can be buffered at the server layer (ie. apache) when serving gzip/compressed responses so even when you do early flushing, content will not be sent until it is complete.
On 21 nov, 12:54, Jordi Boggiano <[email protected]> wrote: > On Sun, Nov 21, 2010 at 3:36 AM, Tim Nagel <[email protected]> wrote: > > > Could you not 'emulate' this by using varnish/ESI technology to build the > > page on the caching webserver and output it gradually? (like have the > > header/footer as their own ESI pages or something?)t > > Yes I was just thinking about that, no matter what we do in the > framework, if we assume the page is buffered by the reverse proxy > cache layer anyway, it won't help much. The best bet is indeed to > deliver a layout as soon as possible, that contains just placeholders, > and then hope that Varnish or whatever other technology starts > flushing early on. Not sure how gzip works out in all that though. I'm > not sure if enabling mod_deflate on apache will buffer the whole > content until it's compressed or if it compresses/flushes it as a > stream. > > 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] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
