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 <[email protected]> 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 <[email protected]> > 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 > > >
