Skip to content
Browse files

Documents change in encoders

git-svn-id: svn://cherokee-project.com/cherokee/trunk@5909 5dc97367-97f1-0310-9951-d761b3857238
  • Loading branch information...
1 parent 47bff75 commit 07a8507a812a943a33cae23c4e5aa2c7b2c24fb4 taher committed Dec 10, 2010
Showing with 7 additions and 1 deletion.
  1. +4 −1 doc/modules_encoders_deflate.txt
  2. +3 −0 doc/modules_encoders_gzip.txt
View
5 doc/modules_encoders_deflate.txt
@@ -8,12 +8,15 @@ link:modules_encoders_gzip.html[gzip] encoder. The `gzip` compression
is technically superior to `deflate`, thus this one is not set up as a
default for new virtual servers.
+A *Compression Level* can be optionally set within the range 0 to 9,
+where 0 is no compression, 1 best speed, and 9 is best compression.
+
Just as with `gzip`, the encoding support is based on modules. The
configuration file must tell the server to load a module or it won't
be supported.
Also, as with `gzip`, it is possible to specify which files can be
-encoded and which ones cannot.
+encoded and which ones are to be excluded.
The only reason to offer `deflate` encoding is for the rare cases in
which it is supported by clients that do not support `gzip`. No modern
View
3 doc/modules_encoders_gzip.txt
@@ -10,6 +10,9 @@ Remember that the encoding support is based on modules. If the
configuration file tells the server to load a module, it will get it
ready to use. Otherwise there won't be any kind of support in memory.
+A *Compression Level* can be optionally set within the range 0 to 9,
+where 0 is no compression, 1 best speed, and 9 is best compression.
+
For example, let's see how it works when the encoder is configured to
handle html files.

0 comments on commit 07a8507

Please sign in to comment.
Something went wrong with that request. Please try again.