Fix Websocket compression tests for Client side.

sdk/lib/io/websocket_impl.dart

Index: sdk/lib/io/websocket_impl.dart
diff --git a/sdk/lib/io/websocket_impl.dart b/sdk/lib/io/websocket_impl.dart
index 297c25b31aece2954ee78c0f6cc14e5bf315f8e1..6189c46faaafd568e8e29401ee10704c30c23a7a 100644
--- a/sdk/lib/io/websocket_impl.dart
+++ b/sdk/lib/io/websocket_impl.dart
@@ -604,6 +604,11 @@ class _WebSocketPerMessageDeflate {
       result.addAll(out);
     }
 
+    if (!serverSide && clientNoContextTakeover) {
+      encoder.end();
+      encoder = null;

[Søren Gjesse, 2016/01/15 08:08:38]

Shouldn't there be similar logic in the other direction, or am I missing
something here?

From the way we create the headers it seems like we always honor both
client_no_context_takeover and server_no_context_takeover. I that case the
server side should also end its decoder when server_no_context_takeover is in
effect.

Likewise the decoder can also be "discarded" when no context takeover is on
effect.

Besides the Autobahn tests it would be great to have some local tests of the
different context take over combinations to ensure that the compression engines
are restarted/reused depending on these flags.

+    }
+
     if (result.length > 4) {
       result = result.sublist(0, result.length - 4);
     }