Implement exponential backoff for failed Me2Me authentication attempts

remoting/webapp/_locales/en/messages.json

Index: remoting/webapp/_locales/en/messages.json
diff --git a/remoting/webapp/_locales/en/messages.json b/remoting/webapp/_locales/en/messages.json
index 23883884cadb85d4eae8720e871d2bbfe7e1fbbe..bdf3554385fa3ee9da7599289260caad12c1c00c 100644
--- a/remoting/webapp/_locales/en/messages.json
+++ b/remoting/webapp/_locales/en/messages.json
@@ -138,6 +138,10 @@
     "message": "An unknown error occurred. Please sign out of Chromoting and try again.",
     "description": "Generic error message, displayed if something went wrong, but we aren't able to determine what, or the cause is too technical to be of use to a typical user."
   },
+  "ERROR_HOST_IS_DISABLED": {
+    "message": "Connections to the remote computer are temporarily blocked because somebody was trying to connect to it with invalid PIN.",

[Jamie, 2012/03/26 21:08:22]

We usually try to give remedy instructions in our error messages. In this case
"Please try again later" might be appropriate.

[Sergey Ulanov, 2012/03/26 23:00:32]

Done.

+    "description": "Error that is shown on the client side when the host is blocking all connections due to failed authentication attempts."
+  },
   "ERROR_HOST_IS_OFFLINE": {
     "message": "The remote computer is not responding to connection requests. Please verify that it is online and try again.",
     "description": "Error that is shown on the client side when we don't get a response from the host."