couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hahn <>
Subject Re: suggestion for improvement
Date Thu, 19 Apr 2012 02:56:05 GMT
I'm sending changed docs from node to the browser.  Then the browser
compares the doc to the dom.   If i only sent doc changes there would be
less net traffic and several many of changes wouldn't need to be sent at

The particular situation that caused me to post this question is a case
where only about 1% of the changes are needed.  It bugs me to have so much
unneeded traffic.

I could cache all the data sent to the client to compare in the server.
 I've also thought of writing a summary of what is changed on writes along
with the document.  I wanted to ask here before I went down any of these
rabbit holes.

On Wed, Apr 18, 2012 at 6:50 PM, Dominic Tarr <>wrote:

> couch just doesn't track things at that level, since versioning is done at
> the document level.
> how are you doing handling this at the moment?
> are you using a library to do a diff of the conflicted versions or
> something like that?
> On Thu, Apr 19, 2012 at 8:28 AM, Mark Hahn <> wrote:
> > Was there a suggestion in the voting list to tell the user what has
> changed
> > when a change notification or conflict is issued?  My app burns a lot of
> > resources because of this problem.
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message