[Android WebView] AwContentsClient.shouldCreate window callback part 2.

android_webview/browser/aw_contents_io_thread_client.h

Index: android_webview/browser/aw_contents_io_thread_client.h
diff --git a/android_webview/browser/aw_contents_io_thread_client.h b/android_webview/browser/aw_contents_io_thread_client.h
index 0dd414623db006fad9cc079441187f97612fc37a..d6a1111a8b5e448f63b456b61469a535fcd5b547 100644
--- a/android_webview/browser/aw_contents_io_thread_client.h
+++ b/android_webview/browser/aw_contents_io_thread_client.h
@@ -43,6 +43,19 @@ class AwContentsIoThreadClient {
   static scoped_ptr<AwContentsIoThreadClient> FromID(int render_process_id,
                                                      int render_view_id);
 
+  // Notifies registered observers when an AwIoThreadClient is registerd
+  // for the specified |child_id| and |route_id|. Invoked on the thread
+  // that the Observer was registered on.
+  class ReadyObserver {
+   public:
+    virtual void OnIoThreadClientReady(int child_id, int route_id) = 0;

[joth, 2012/11/16 21:52:57]

protected virtual d'tor.

[benm (inactive), 2012/11/28 20:00:05]

Done.

+  };
+
+  // Add/remove an observer that will be notified as AwIoThreadClients
+  // are registered.
+  static void AddReadyObserver(ReadyObserver* obs);
+  static void RemoveReadyObserver(ReadyObserver* obs);

[joth, 2012/11/16 21:52:57]

document which thread these must be called on, and which thread you'll receive
the callback on.

[benm (inactive), 2012/11/28 20:00:05]

Would do, but I think I'm going to go with your suggestion of keeping the map
"dumb" and have AwContents call into the AwResourceDispatcherHostDelegate. For
completeness though, you can call on any thread and you will be called back on
the thread that you call on.

+
   // This method is called on the IO thread only.
   virtual scoped_ptr<InterceptedRequestData> ShouldInterceptRequest(
       const GURL& location,