Resolving replication conflicts entirely within CouchDB

Is it possible to resolve conflicts caused by database replication entirely within CouchDB? I know it has its own internal algorithm for deciding which revision to use, but can an application register a custom javascript function to deal with conflicts in an application-specific way?

The CouchDB guide and wiki both seem only to suggest using ext开发者_JAVA百科ernal application code to resolve conflicts.

---

No, it is not possible to resolve conflicts automatically (or triggered somehow) within CouchDB.

It always up to the developers, to resolve conflicts, that's true.

In MVCC system automatic conflict resolution feels awkward. What for do we store the previous versions and grant non locking access?

(Correct me if I am wrong, please)