Implementation of shared worker code path for WebView file system permission.

content/public/browser/content_browser_client.h

Index: content/public/browser/content_browser_client.h
diff --git a/content/public/browser/content_browser_client.h b/content/public/browser/content_browser_client.h
index d29b30ee2e539c58c5e1f731d13ee1ddde766533..7e1c1b4d1e4e00b66c7e353a2a7e1c437dc55dab 100644
--- a/content/public/browser/content_browser_client.h
+++ b/content/public/browser/content_browser_client.h
@@ -345,10 +345,11 @@ class CONTENT_EXPORT ContentBrowserClient {
   // Allow the embedder to control if access to file system by a shared worker
   // is allowed.
   // This is called on the IO thread.
-  virtual bool AllowWorkerFileSystem(
+  virtual void RequestWorkerFileSystemAccessSync(

[jam, 2014/06/19 16:47:27]

I'm confused, this has a Sync suffix but takes a callback. should it be Async?

[Fady Samuel, 2014/06/19 16:50:11]

This is for the sync filesystem API. For webview's case, we're simply blocking
the guest until the embedder makes a permission decision, hence the callback.
This is a delayed response.

[Xi Han, 2014/06/19 17:22:27]

The name comes from the webview guest, whether the guest calls a sync api or
async filesystem API. Now we have both APIs:
1) sync API for a request from shared worker & worker (the request will block
workers);
2) async API for a request from a webview guest main thread (request
won't block main thread).
We use a sync IPC message (WorkerProcessHostMsg_RequestFileSystemAccessSync) to
send request.

       const GURL& url,
       ResourceContext* context,
-      const std::vector<std::pair<int, int> >& render_frames);
+      const std::vector<std::pair<int, int> >& render_frames,
+      base::Callback<void(bool)> callback);
 
   // Allow the embedder to control if access to IndexedDB by a shared worker
   // is allowed.