Thank you for the quick answer. > I think new streaming interfaces are the way to go. We’ve been talking about > them in other contexts like replication before. We won’t likely get to this > before 2.0, though.
Is that included in the developer preview? > Or write the doc validation in Erlang. I wish i could do that but my skills stuck at the Erlang 101. I have seen an Erlang implementation that supports json-schema Draft 3 - i will analyse whether our schemas using Draft 4 related definitions or not. An other question came into my mind. Is the JS code of a design doc (here the validate_doc_update.js) already evaluated (maybe after the doc save action) or gets it evaluated for every single doc again? When it is the second i would see some smaller optimisation potentials in my current implementation (e.g. bigger docs are more performant to validate then the same amount split into smaller pieces) ingo
smime.p7s
Description: S/MIME cryptographic signature
