Add host-side rate-limiting to desktop resize events.

remoting/webapp/client_session.js

Index: remoting/webapp/client_session.js
diff --git a/remoting/webapp/client_session.js b/remoting/webapp/client_session.js
index f40fa850addd071aff82e537e50b808fc90817c3..c6e800ec49fad85d0d5980d50c37abf1191c52a2 100644
--- a/remoting/webapp/client_session.js
+++ b/remoting/webapp/client_session.js
@@ -885,7 +885,7 @@ remoting.ClientSession.prototype.onResize = function() {
                                                 window.innerWidth,
                                                 window.innerHeight,
                                                 window.devicePixelRatio),
-        1000);
+        250);

[Jamie, 2013/06/03 23:26:28]

250ms seems to be a good compromise between sending the resize command as soon
as possible after the user stops dragging the window border and not sending
erroneous resize commands while s/he is still doing so (sending resize commands
too early is bad because it causes the host-side rate-limiting to kick in,
delaying resizing the desktop to the intended size).

[alexeypa (please no reviews), 2013/06/04 00:05:26]

Consider using different timeout depending on the kind of the host we are
connected. The timeout should be shorter for the host implementing
rate-limiting. 

A new capability needs to be added to the host and webapp to be able to do that.
Look for 'sendInitialResolution' to see how it is done. The only caveat is that
this new capability should be returned by all implementation of
DesktopEnvironment::GetCapabilities().

[Jamie, 2013/06/04 01:27:49]

Done.

   }
 
   // If bump-scrolling is enabled, adjust the plugin margins to fully utilize