It should be pretty straightforward to enable specialized content encoding.
支持专门的内容编码应是相当容易的。
From the server side, there are two ways to deal with the content encoding.
在服务器端有两种处理内容编码的方式。
The IETF's standard for compressing HTTP contents includes two levels of encoding: content encoding and transfer encoding.
IETF用来压缩HTTP内容的标准包括两级编码：内容编码和传输编码。
Furthermore, this article looks at encoding at the servlet level, which will enable you to implement a different content encoding scheme.
此外，本文将讨论servlet级别上的编码，它使您可以实现不同的内容编码方案。
Content encoding applies to methods of encoding and compression that have been already applied to documents before the Web user requests them.
内容编码是指在Web用户请求文档之前就已经应用到这些文档的编码和压缩方法。
When the server sends back the resulting content, the Content-Encoding header reveals to the browser the format used to compress the content.
当服务器发送回生成的内容时，Content - encoding头向浏览器说明压缩内容所用的格式。
The Content-Encoding header tells the browser that the response body is compressed using the gzip algorithm. After decompressing the blob, you’ll see the HTML you’d expect
内容编码头告诉浏览器整个响应体用gzip算法进行压缩。
The Content-Encoding header tells the browser that the response body is compressed using the gzip algorithm. After decompressing the blob, you’ll see the HTML you’d expect
内容编码头告诉浏览器整个响应体用gzip算法进行压缩。
应用推荐