I have no idea what these are for - perhaps because in the old protocol the
wavelet id field was not optional, and non-wavelet updates (like channel ids)
needed to fill it in?
In any case, these dummy wavelets are unnecessary with the new protocol. I'm
mainly filing this bug to give a reference against which the hack code in the
client can be marked.
Original issue reported on code.google.com by hearn...@google.com on 26 Oct 2010 at 5:45
Original issue reported on code.google.com by
hearn...@google.com
on 26 Oct 2010 at 5:45