Private API for extensions like ssh-client that need access to TCP.

chrome/common/extensions/api/extension_api.json

Index: chrome/common/extensions/api/extension_api.json
diff --git a/chrome/common/extensions/api/extension_api.json b/chrome/common/extensions/api/extension_api.json
index 936792791180a806d71573915513b48c4f76b47c..0f30a5f392636b88c68004007775b5df41207eaf 100644
--- a/chrome/common/extensions/api/extension_api.json
+++ b/chrome/common/extensions/api/extension_api.json
@@ -4683,6 +4683,34 @@
     ]
   },
   {
+    "namespace": "webproxyPrivate",

[Aaron Boodman, 2011/04/07 03:17:01]

I just realized this: we already have a 'proxy' API in the extension system that
this might get confused with. Can you think of a better name?

What about just renaming chromeOSInfoPrivate.get to chromeosPrivate.getInfo, and
then renaming this to chromeOSPrivate.getTCPProxyToken() ?

[Denis Lagno, 2011/05/13 22:02:53]

I've renamed to webSocketProxyPrivate.getPassportForTCP

+    "nodoc": true,
+    "types": [],
+    "functions": [
+      {
+        "name": "getToken",
+        "type": "function",
+        "description": "requests authorization token for websocket to TCP proxy.",
+        "parameters": [
+          {
+            "name": "hostname",
+            "type": "string",
+            "minLength": 1,
+            "description": "hostname to which TCP connection is requested."
+          },
+          {
+            "name": "port",
+            "type": "integer",
+            "minimum": 1,
+            "maximum": 65535,
+            "description": "TCP port number."
+          }
+        ]
+      }
+    ],
+    "events": []
+  },
+  {
     "namespace": "experimental.extension",
     "types": [
       {