Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 13039 invoked from network); 8 Nov 2010 22:11:23 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Nov 2010 22:11:23 -0000 Received: (qmail 88710 invoked by uid 500); 8 Nov 2010 22:11:51 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 88675 invoked by uid 500); 8 Nov 2010 22:11:51 -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 88667 invoked by uid 99); 8 Nov 2010 22:11:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 22:11:51 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mikeal.rogers@gmail.com designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vw0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 22:11:46 +0000 Received: by vws20 with SMTP id 20so569834vws.11 for ; Mon, 08 Nov 2010 14:11:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=aluvwO2qlhXbo4XVo1bSAWo5ABzTJU5GogEE8KeiHfk=; b=BJpI1tiQY0zt6odRYwKWNnS1w6RhhWRX7ektBAmmBtuYDGca/acibHqAseIkwWylfa ACGOvJiyibzCx/2G3JzbqOlqd0TDQel3mC0T04ECx4qWWX4eihWRszqXkT2JIvLmhY08 0ujJyqpwo+pbKR0fs54Ed6QrojKBCdj2FpeCI= 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; b=BSiTS4WrbIe2AIFCl7KDsGU4ybUKJBrN5aclPI1Hr71zjJQrTOr/5r1TiqSMgq11qF IYpTISGN1pr2ApoTcFSetTMH7Wjb4jLl0iYKbS8JKYDA+ffMDpvj/VAY8O3ZHjSzuLpq 2ho60uqCusjAZhrCDpVKbJjrDz7omJ+sTkPf0= MIME-Version: 1.0 Received: by 10.224.135.208 with SMTP id o16mr4337713qat.252.1289254285626; Mon, 08 Nov 2010 14:11:25 -0800 (PST) Received: by 10.229.185.85 with HTTP; Mon, 8 Nov 2010 14:11:25 -0800 (PST) In-Reply-To: References: <4CD86A82.6040305@arcor.de> Date: Mon, 8 Nov 2010 14:11:25 -0800 Message-ID: Subject: Re: LivelyCouch - a framework around CouchDB and Node.js From: Mikeal Rogers To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=000e0cd11464b84e2b049491e735 --000e0cd11464b84e2b049491e735 Content-Type: text/plain; charset=ISO-8859-1 Yeah, this stuff is amazing because it implements things that were in my head and I didn't write it :) I'm super happy right now ;) On Mon, Nov 8, 2010 at 2:09 PM, Gabriel Farrell wrote: > Neat. I look forward to both using the framework and learning from its > use of externals and http proxy modules. Comments: > > Because the handlers are similar to views, I'm tempted to want them in > my design documents. Would it be possible to read them from a > "handlers" value there? > > I think that URL example at the end of Part 1 should be > "filtered_people" instead of "blond_people". > > I like the way Mikeal talked about triggering events in his "Crazy > Delicious" talk at JSConf by giving each trigger its own document, > firing events off a long poll of _changes, then updating that document > with event responses. How would LivelyCouch notify an app with event > responses? > > > Gabriel > > On Mon, Nov 8, 2010 at 4:24 PM, Mirko Kiefer > wrote: > > Hi, > > we are currently working on open sourcing our so called LivelyCouch > > framework which emerged out of a few projects. > > Hopefully this week still we will have a website up and running > explaining > > the usage of LivelyCouch in more detail. > > I would just like to get some early feedback on our concepts - so I wrote > a > > little summary in two parts on my blog. > > > > The first part focuses on writing Node.js handlers: > > > http://mirkokiefer.com/blog/2010/11/introducing-livelycouch-part-1-writing-node-js-handler/ > > > > Part two explains the event system we built around CouchDB using Node: > > > http://mirkokiefer.com/blog/2010/11/introducing-livelycouch-part-2-events-and-workers/ > > > > Hope to get a lot of feedback! > > > > Mirko > > > --000e0cd11464b84e2b049491e735--