Hey Alex, Your question is a great question, and unfortunately a hard one to answer without more knowledge of your particular application, data structure and intended usage.
Unfortunately I couldn't access your application without making an account - and i don't speak german so i couldn't fill out the fields correctly :/ But in regards to your question, there are incredible amount of ways to handle your problem. Keeping track of revisions with a particular document shouldn't be a problem (just store the returned _rev key somewhere) and update accordingly. Alternatively, you could bypass the whole _rev check with a clever update function. (if you need help with these feel free to ask) However, it sounds like data usage is your biggest concern (im assuming this is a mobile application). In which case, have you thought about doing a setTimeout on field changes? for example, when a field changes, delay the sending of the update by a minute. If a new field changes, clear the previous timeout, and start a new '1 minute countdown' to send the data. The data sent should only be the keys the change in the document, and it should call an update function. This will cut down on data usage as well (it won't send the WHOLE document, just what needs to be updated). But honestly, if data usage is not a concern, couchdb is more than up to the task for handling A LOT of document revisions. hope that helped somewhat, -Pete
