[
https://issues.apache.org/jira/browse/COUCHDB-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230498#comment-15230498
]
Robert Newson commented on COUCHDB-1749:
----------------------------------------
In 2.0, you can send request bodies already gzipped;
echo '{"foo":true}' | gzip | curl -s foo:bar@localhost:15984/db1/doc3 -XPUT -T
- -Hcontent-encoding:gzip
{"ok":true,"id":"doc3","rev":"1-89248382088d08ccb7183515daf390b8"}
curl -s foo:bar@localhost:15984/db1/doc3
{"_id":"doc3","_rev":"1-89248382088d08ccb7183515daf390b8","foo":true}
> Add an optional HTTP compression layer to CouchDB
> -------------------------------------------------
>
> Key: COUCHDB-1749
> URL: https://issues.apache.org/jira/browse/COUCHDB-1749
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Dave Cottlehuber
> Labels: gsoc, mentor
>
> It would be really cool if you could do the compression during doc update (or
> view
> creation or something) so that it can be served directly next time.
> See https://github.com/lgerbarg/couchdb/tree/gzip-support for a prior
> implementation or https://gist.github.com/archaelus/76455 for a
> file-based approach, and
> http://visualstart.blogspot.com/2012/02/mochiweb-erlang-and-gzip.html
> for some other ideas.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
