JSR-356 - Handling ClientContainer.setMax(Text|Binary)MessageBufferSize better

+ The Jetty API is more configurable than the JSR, this forces the
   Jetty side API to be consistent for whatever value the end user
   specifies.

jetty-websocket/javax-websocket-client-impl/src/main/java/org/eclipse/jetty/websocket/jsr356/ClientContainer.java

@@ -282,13 +282,14 @@ public class ClientContainer implements WebSocketContainer
     @Override
     public void setAsyncSendTimeout(long timeoutmillis)
     {
+        client.setMaxIdleTimeout(timeoutmillis);
         client.setAsyncWriteTimeout(timeoutmillis);
     }
 
     @Override
     public void setDefaultMaxBinaryMessageBufferSize(int max)
     {
-        // TODO: add safety net for policy assertions
+        client.getPolicy().setMaxBinaryMessageSize(max);
         client.setMaxBinaryMessageBufferSize(max);
     }
 
@@ -301,7 +302,7 @@ public class ClientContainer implements WebSocketContainer
     @Override
     public void setDefaultMaxTextMessageBufferSize(int max)
     {
-        // TODO: add safety net for policy assertions
+        client.getPolicy().setMaxTextMessageSize(max);
         client.setMaxTextMessageBufferSize(max);
     }