Pass handle of the native view window to the native messaging host.

chrome/test/data/native_messaging/native_hosts/echo.py

Index: chrome/test/data/native_messaging/native_hosts/echo.py
diff --git a/chrome/test/data/native_messaging/native_hosts/echo.py b/chrome/test/data/native_messaging/native_hosts/echo.py
index a4471c7cbb4d4fe96037b3ebb7887215850dd5b7..e9550f6cf678f7831b2617c03b3e39f23a6f7dfe 100755
--- a/chrome/test/data/native_messaging/native_hosts/echo.py
+++ b/chrome/test/data/native_messaging/native_hosts/echo.py
@@ -25,7 +25,10 @@ def Main():
   if len(sys.argv) < 2:
     sys.stderr.write("URL of the calling application is not specified.\n")
     return;
-  caller_url = sys.argv[1]
+  for arg in sys.argv[1:]:

[Sergey Ulanov, 2013/08/08 18:22:37]

I think it's better to keep this test as it was. Existing native hosts may
depend on order of arguments. Also this code only handles the case when args are
specified as "--arg=value", but not "--arg value".

[alexeypa (please no reviews), 2013/08/08 23:57:41]

To recap our offline conversation. It is very convenient to use CommandLine. It
does proper quoting on Windows and required to start the process on Posix.
Unfortunately it reorders the switches and arguments such that switches go
first.

I believe changing the order of the command line arguments has minimal potential
to break existing hosts for two reasons:

1. Native messaging has been enabled in m29 that is not yet reached stable.
2. The command line format has not been documented yet.
That should be good enough for now, because we know that the command line is
produced by CommandLine.

+    if not arg.startswith('--'):
+      caller_url = arg
+      break
 
   while 1:
     # Read the message type (first 4 bytes).