Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 71418 invoked from network); 16 Aug 2009 17:28:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Aug 2009 17:28:35 -0000 Received: (qmail 64058 invoked by uid 500); 16 Aug 2009 17:28:40 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 63951 invoked by uid 500); 16 Aug 2009 17:28:40 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 63941 invoked by uid 99); 16 Aug 2009 17:28:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Aug 2009 17:28:40 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com designates 209.85.210.204 as permitted sender) Received: from [209.85.210.204] (HELO mail-yx0-f204.google.com) (209.85.210.204) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Aug 2009 17:28:32 +0000 Received: by yxe42 with SMTP id 42so3386942yxe.13 for ; Sun, 16 Aug 2009 10:28:11 -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=0CJHVHOn6ylV7qmwuGajbKxO2BuiL4ZSiXpNRAqTCTc=; b=NUjfPjVR1LWCSJfz2CqUBGCHdjNmewKUWtBjkql/QXQcfrDID/+U7LqMwKIYRnbNdO LUmJ3VaNttwiB+JIcu4DNrzVxUhbDVnjf1YLslCJyyUMJQsUFjj4vvthIDRYhGQmBAPe HErw/LeI70aU+awvD/OILTP44uLUzlW04XoAE= 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=K+/qFYo4kL4SjEWN5UjfeTRH2djjU8zChYw9w3OtXh5+mr2kRUa2XSHippJgtYY2Tr 0F7WmseKketcQJg/gp5s0XpAq4D8sRZD0rACLEsqvtOvKpwo+YaTNBNBgvdHPVJvxeZp 5CtB5FMk4POsxosV5F9/KysXPI5pQ4YcRist4= MIME-Version: 1.0 Received: by 10.101.51.7 with SMTP id d7mr2769399ank.106.1250443691652; Sun, 16 Aug 2009 10:28:11 -0700 (PDT) In-Reply-To: References: <21606dcf0908151121p14ee0838x4f7fa3186f20736d@mail.gmail.com> <21606dcf0908151534x362322n3c1e02dbb46baf5d@mail.gmail.com> Date: Sun, 16 Aug 2009 13:28:11 -0400 Message-ID: Subject: Re: Validation callouts over HTTP[S] From: Paul Davis To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Sun, Aug 16, 2009 at 12:19 PM, Delta 2038 wrote: > On Sat, Aug 15, 2009 at 8:24 PM, Paul Davis wrote: > > validate_doc_update functions probably won't ever be able to access >> anything outside of the data provided in the function signature. >> Allowing a validator to access external resources could end up causing >> lots of weirdness during replication and what not. >> >> That said, the new _update handlers may be open to having HTTP >> support. I'm not entirely certain on the implications here and if we >> do allow it, we'll have to revisit some of the curl handlers. > > > Are these _update handlers present in 0.9.x or an upcoming release? Where > can I find more information about what they are and how to use them? We're > looking for ways to handle server-side processing of input data such as > modification timestamps, etc. If that's something the _update handlers can > perform, that eliminates at least part of the need to have say a reverse > proxy that's capable of massaging the input data sitting in front of > CouchDB. > > Thanks. > They were just committed a couple days ago. I haven't seen anyone create a Wiki page so as usual the best documentation is in the unit tests. Paul