|
: -8 : 2 : 10 |
I wish we could specify some sort of "replication priority" on view level. The purpose is that the designer can to some extent tell the replicator what documents that should be replicated first. For example may a view full of configuration documents be more important to the functionallity of the database, compared to ordinary views with data documents. We've had scenarios where end users see that the replication may take longer than they guessed it would take ("hey, I just replicate before leaving for the train station ..."), and they just terminate the replication at some point. Then, if important configuration documents didn't make it, they database may not work as intended locally any more... I envision some sort of "priority number", where the default number leavs all documents in those views unaffected about priorty. Then I could define my config document view as "1", my translation document view as "2" and so forth. |