From dev-return-6629-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Thu Sep 24 02:14:11 2009 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 18067 invoked from network); 24 Sep 2009 02:14:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Sep 2009 02:14:11 -0000 Received: (qmail 70104 invoked by uid 500); 24 Sep 2009 02:14:11 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 70024 invoked by uid 500); 24 Sep 2009 02:14:11 -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 70014 invoked by uid 99); 24 Sep 2009 02:14:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Sep 2009 02:14:10 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com designates 209.85.132.244 as permitted sender) Received: from [209.85.132.244] (HELO an-out-0708.google.com) (209.85.132.244) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Sep 2009 02:14:01 +0000 Received: by an-out-0708.google.com with SMTP id b2so477804ana.5 for ; Wed, 23 Sep 2009 19:13:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=DNR/LMmltET5VRlsCrAk6cuqyCaWGyQuePE8iwUFz5U=; b=nMFYibXuRjNjj4gXYCWKH/erNH5CLUXTFvaomwX1xAgwu31M1eAl6sPXM0UUjflfI9 Q5HrFSrRohJwbhK2GkMj8t43M1bf2Jn83UqFqpiWYEDVGERSOMKH8hT6LjcsRNAnPfrU 5h9uY6nkGhyL3sIV5FZrv/oF6xKey4Lbm0ANk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=tI2Tzej9MYqMvP3y+M8KjfGaGcxdTdFM2JDMjwclaoyDznj6uvl/2OzODDVot2h4mi ArpDvzyX0SSc2xPvfDfnAyDbVPS6yJstANvAyKSsUdIMykdzNKHgflDiPa7heEztpgcB +UnRccW31c2ESG2fRjOvcQMTfpQ3ABxkkd8g4= MIME-Version: 1.0 Received: by 10.101.181.26 with SMTP id i26mr3439065anp.56.1253758420777; Wed, 23 Sep 2009 19:13:40 -0700 (PDT) In-Reply-To: <87E5619A-3E2D-407F-9414-D9AFCC9E0FF5@apache.org> References: <87E5619A-3E2D-407F-9414-D9AFCC9E0FF5@apache.org> Date: Wed, 23 Sep 2009 22:13:40 -0400 Message-ID: Subject: Re: CRLF or LF in our JSON? From: Paul Davis To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Is there a preference for text/plain or HTTP or somewhere we can default the decision to? It seems fairly arbitrary. I do remember someone saying just the other day that not having \r\n for changes meant that Twisted didn't work out of the box. I think it was Mark or Beno=EEt. Paul On Wed, Sep 23, 2009 at 10:02 PM, Adam Kocoloski wrot= e: > Hi, I noticed we're fairly inconsistent in the line terminators that we u= se: > views use \r\n, _changes uses \n, etc. =A0I guess we should standardize o= n one > or the other. =A0Anybody have a preference? =A0Best, > > Adam >