On 21.11.2010, at 12:54, Jordi Boggiano 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.
afaik varnish doesnt like you using gzip, though maybe it can compress things itself. as for chunked response with varnish, it seems this is planned for 3.0 which is expected within the next 6 months. do note that they are calling a "ESI include block" a "chunk" and therefore the preferred terminology for this in the context of varnish is "streaming" support. it doesnt seem however like there are any public design documents for this feature. but it may or may not add chunked/streaming response to a standard Symfony2 setup. i guess we have to wait an see and keep a close eye on what happens over there. regards, Lukas Kahwe Smith [email protected] -- 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
