Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2B29DF164 for ; Wed, 27 Mar 2013 16:27:16 +0000 (UTC) Received: (qmail 78438 invoked by uid 500); 27 Mar 2013 16:27:15 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 78404 invoked by uid 500); 27 Mar 2013 16:27:15 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 78393 invoked by uid 99); 27 Mar 2013 16:27:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Mar 2013 16:27:15 +0000 Date: Wed, 27 Mar 2013 16:27:15 +0000 (UTC) From: "Dave Cottlehuber (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (COUCHDB-1749) Add an optional HTTP compression layer to CouchDB MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Dave Cottlehuber created COUCHDB-1749: ----------------------------------------- Summary: 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira