[PPAPI] It is now possible to pass filesystems from JavaScript to NaCl modules.

ppapi/shared_impl/var_tracker.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef PPAPI_SHARED_IMPL_VAR_TRACKER_H_
 #define PPAPI_SHARED_IMPL_VAR_TRACKER_H_
 
 #include <vector>
 
 #include "base/basictypes.h"
 #include "base/containers/hash_tables.h"
 #include "base/memory/ref_counted.h"
 #include "base/memory/scoped_ptr.h"
 #include "base/memory/shared_memory.h"
 #include "base/threading/thread_checker.h"
 #include "ppapi/c/pp_instance.h"
 #include "ppapi/c/pp_module.h"
 #include "ppapi/c/pp_resource.h"
 #include "ppapi/c/pp_var.h"
 #include "ppapi/shared_impl/host_resource.h"
 #include "ppapi/shared_impl/ppapi_shared_export.h"
 #include "ppapi/shared_impl/var.h"
 
+namespace IPC {
+class Message;
+}  // namespace IPC
+
 namespace ppapi {
 
 class ArrayBufferVar;
 
 // Tracks non-POD (refcounted) var objects held by a plugin.
 //
 // The tricky part is the concept of a "tracked object". These are only
 // necessary in the plugin side of the proxy when running out of process. A
 // tracked object is one that the plugin is aware of, but doesn't hold a
 // reference to. This will happen when the plugin is passed an object as an
@@ skipping 44 matching lines @@
   // into the new array buffer.
   PP_Var MakeArrayBufferPPVar(uint32 size_in_bytes,
                               base::SharedMemoryHandle h);
 
   // Create an ArrayBuffer and copy the contents of |data| in to it. The
   // returned object has 0 reference count in the tracker, and like all
   // RefCounted objects, has a 0 initial internal reference count. (You should
   // usually immediately put this in a scoped_refptr).
   ArrayBufferVar* MakeArrayBufferVar(uint32 size_in_bytes, const void* data);
 
+  // Creates a new resource var from a resource creation message. Returns a
+  // PP_Var that references a new PP_Resource, both with an initial reference
+  // count of 1. On the host side, |creation_message| is ignored, and an empty
+  // resource var is always returned.
+  virtual PP_Var MakeResourcePPVarFromMessage(
+      PP_Instance instance,
+      const IPC::Message& creation_message,
+      int pending_renderer_id,
+      int pending_browser_id) = 0;
+
   // Creates a new resource var that points to a given resource ID. Returns a
   // PP_Var that references it and has an initial reference count of 1.
   // If |pp_resource| is 0, returns a valid, empty resource var. On the plugin
   // side (where it is possible to tell which resources exist), if |pp_resource|
   // does not exist, returns a null var.
   PP_Var MakeResourcePPVar(PP_Resource pp_resource);
 
   // Creates a new resource var that points to a given resource ID. This is
   // implemented by the host and plugin tracker separately, because the plugin
   // keeps a reference to the resource, and the host does not.
@@ skipping 123 matching lines @@
   // other threads (especially the IO thread). On the plugin side, the tracker
   // is protected by the proxy lock and is thread-safe, so this will be NULL.
   scoped_ptr<base::ThreadChecker> thread_checker_;
 
   DISALLOW_COPY_AND_ASSIGN(VarTracker);
 };
 
 }  // namespace ppapi
 
 #endif  // PPAPI_SHARED_IMPL_VAR_TRACKER_H_