Transfer-Encoding：chunked [英] Transfer-Encoding: chunked

问题描述

我试图更多地了解 Transfer-Encoding：chunked 。推荐一些文章：
http://zoompf.com/blog/2012/05 / too-chunky 和Transfer-Encoding：chunked PHP中的标题。

I was trying to understand more on Transfer-Encoding:chunked. referred some articles: http://zoompf.com/blog/2012/05/too-chunky and "Transfer-Encoding: chunked" header in PHP.

我仍然没有得到非常清晰的图片。我理解设置此编码允许服务器将块中的内容设置为浏览器并导致部分呈现内容，使网站响应。

I still didn't get very clear picture. I understand setting this encoding allows server to set content in chunk to the browser and cause partial rendering of content at a time that makes web site responsive.

如果我有在IBM WAS上托管的提供动态内容的Web应用程序（例如：基于JSF的Web应用程序），大多数Web页面都设计为服务器丰富的静态内容，包含大量CSS和JS文件+动态内容。如何为我的页面设置transfer-encoding'chunked'？或换句话说：

If I've a web application that serves dynamic content (ex: JSF based web app) hosted on IBM WAS, most of the web pages are designed to server rich static content with lots of CSS and JS files + dynamic content. How can I set transfer-encoding 'chunked' for my pages? Or in other words:

• 您如何决定哪个页面'Transfer-Encoding：chunked'以及如何为该页面设置它？

• How do you decide which page will have 'Transfer-Encoding: chunked' and how do you set it for that page?

您的个人经历对我的理解肯定是有价值的。

Your personal experience will certainly be valuable for my understanding.

推荐答案

渐​​进式渲染不需要Transfer-Encoding：chunked 。但是，如果在发送第一个字节之前未知总内容长度，则需要 。

Transfer-Encoding: chunked isn't needed for progressive rendering. However, it is needed when the total content length is unknown before the first bytes are sent.

这篇关于Transfer-Encoding：chunked的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！