On Wed, Aug 6, 2008 at 1:01 PM, Chris Anderson <[EMAIL PROTECTED]> wrote: > The event system could be prototyped by eavesdropping on the > communication between CouchDB and the view server, and firing events > based on the emitted keys. >
replying to myself... the problem with the event approach is that you get some data lag - those emit() events aren't fired until the view is requested. That means if you have a remap based on a rarely accessed map view, the remap could be stale but not marked as such, until the view is accessed. Your solution (associating doc-ids and revs with rows in the remap index) is nice in that you can just watch the change history of the database to see if any of the associated documents were touched. -- Chris Anderson http://jchris.mfdz.com
