> > Clearly, in BigCouch, you could not depend on the changes feed to > ensure you process an item exactly once, so I suggest its a bad > practice to assume the same of CouchDB. Instead, I would create a view > that includes unprocessed items. Once processed (whatever that > entails), update the document to indicate it has been processed. This > will work everywhere. >
So the view of items to be processed becomes the "global state". That make sense! I suppose once the view of to-be-processed items becomes empty the workers could wait for _changes.
