Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.132.242 as permitted sender)
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=MBgE3a1zRVGKnvMrke60D2uDo1c0rLk1NldKmVd70q2BhM7/pqi9Gkbw4YQQcPWYgA
         oqXzs+06E5o3LBr26LReQj48Jev1yRP53GMUKPcXwgs/p1MjQSUDbg9DHSUHI/QNMoBG
         IdN3j33Ezdfk93OaPene1RizcA2PsuewgYiOE=
MIME-Version: 1.0
In-Reply-To: <f728979f0904231326g34c91ce3k3996eeee20578187@mail.gmail.com>
References: <f728979f0904231326g34c91ce3k3996eeee20578187@mail.gmail.com>
Date: Thu, 23 Apr 2009 17:28:36 -0400
Message-ID: <e2111bbb0904231428w756d1a85q77b0c9c3b02f8e58@mail.gmail.com>
Subject: Re: Update Notifiers
From: Paul Davis <paul.joseph.davis@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Zach,

I haven't tested this at all, but the only way you could affect
CouchDB in an update notifier would be if you didn't read from stdin
often enough. Eventually (I'm pretty sure) the Erlang process that's
sending notifications would block on the write. After a given amount
of time (default is 5 seconds IIRC) the Erlang process would receive a
timeout error from the os_process module.

I think, caveats apply, untested, etc etc.

Paul Davis

On Thu, Apr 23, 2009 at 4:26 PM, Zachary Zolton
<zachary.zolton@gmail.com> wrote:
> Devs,
>
> Does an update notifier script cause any processing in CouchDB to
> block, other than subsequent update notifications?
>
>
> Cheers,
>
> Zach
>