Wave-in-a-box client does client-side id-filtering of protocol updates.

[GoogleCodeExporter]

RemoteWaveViewService drops incoming updates that do not match the id filter 
with which the wave stream was opened.  This logic should be unnecessary if the 
server is already doing the filtering.

@Alex: if you can confirm that the server should not be sending updates for 
wavelets that don't match the id-filter, I'll just delete the client-side 
filtering code.

Original issue reported on code.google.com by hearn...@google.com on 26 Oct 2010 at 5:38

[GoogleCodeExporter]

The server does do filtering, so I think it's safe to remove. Note that the 
first cut of the new protocol may not perform filtering of the snapshot fetch 
request - that may require simple client-side filtering, but probably in a 
different place to where it's done now anyway.

Original comment by ano...@google.com on 26 Oct 2010 at 5:59