Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 17753 invoked from network); 22 Aug 2010 17:16:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Aug 2010 17:16:45 -0000 Received: (qmail 94639 invoked by uid 500); 22 Aug 2010 17:16:45 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 94585 invoked by uid 500); 22 Aug 2010 17:16:44 -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 94577 invoked by uid 99); 22 Aug 2010 17:16:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Aug 2010 17:16:44 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.72.192.234] (HELO fmmailgate03.web.de) (217.72.192.234) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Aug 2010 17:16:38 +0000 Received: from smtp06.web.de ( [172.20.5.172]) by fmmailgate03.web.de (Postfix) with ESMTP id 0986E15DF0591 for ; Sun, 22 Aug 2010 19:16:06 +0200 (CEST) Received: from [84.154.31.95] (helo=[192.168.2.12]) by smtp06.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.110 #24) id 1OnE9M-0008So-00 for dev@couchdb.apache.org; Sun, 22 Aug 2010 19:16:04 +0200 Subject: Re: COUCHDB-864 and 1.0.x From: Klaus Trainer To: dev@couchdb.apache.org In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Sun, 22 Aug 2010 19:16:00 +0200 Message-ID: <1282497360.14749.13.camel@devil> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: klaus.trainer@web.de X-Sender: klaus.trainer@web.de X-Provags-ID: V01U2FsdGVkX1+4kGw1AarH0nTG9GhshVCnY5a5TBn6gy43aY84 TeRFZWRnb680N6ljRB1QqlaOI1CgfomnbvH12VCZszkD8OuVFl /lE1vWYyGvih6tPqN/sg== +1 As soon as there's an adequate test. I'm quite curious about that test ;). -Klaus On Sun, 2010-08-22 at 14:34 +0100, Robert Newson wrote: > All, > > I committed a one-line fix (suggested by Adam) to trunk which now > allows multipart/related PUT's to succeed without mochiweb closing the > connection. At base, mochiweb uses a process dictionary variable to > keep track of whether it ought to close the connection or not. Because > we use the request from a different process, part of that handling is > skipped, causing mochiweb to close a connection when it shouldn't. The > fix (or, less charitably, *hack*) fixes that issue. > > I've struggled to write an etap test that demonstrates the original > problem (the bug was discovered when doing performance testing from a > node.js-based test program) and I feel I owe one. I would like this > patch to land on 1.0.x where I think a confirming test is mandatory. > > I'll continue trying to write the test and will put it to trunk once I > have it. In the meantime, I would like to hear from others about > whether this should go to 1.0.x? It allows efficient and atomic > insertion of documents with attachments, which is an important feature > for me, though to date it is only used by the replicator. > > B.