couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filipe David Manana <fdman...@gmail.com>
Subject Re: standalone attachments and content-encoding header
Date Tue, 23 Mar 2010 00:24:20 GMT
On Tue, Mar 23, 2010 at 12:09 AM, Filipe David Manana <fdmanana@gmail.com>wrote:

>
>
> Also, supporting multiple content-encodings would imply doing some changes
> to the code introduced in ticket 639 (applied to trunk only) which adds a
> new doc query parameter ?att_gzip_length=true. (replacing it with 2
> parameters such as encoding=<encoding_name> and encoded_length=123).
>

Here I meant:

1) renaming doc query param "att_gzip_length" to something like
"att_encoded_length"
2) replacing the attachment stub field "gzip_length" with the 2 fields
"encoding" and "encoded_length"

Overall there are only 4 content encodings defined in the http rfc 2616:
identity, gzip, deflate (zlib's default) and compress (Lempel-Ziv
compression)

-- 
Filipe David Manana,
fdmanana@gmail.com

"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message