diff options
author | brettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-18 21:58:02 +0000 |
---|---|---|
committer | brettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-18 21:58:02 +0000 |
commit | 4d2efd2e100bc961d3e19e0a6f242c7914917690 (patch) | |
tree | c29e1a627687c0ef29a207378ff19fcd9927fb67 /content/ppapi_plugin/plugin_process_dispatcher.cc | |
parent | 6fa9e6f0c0fd3a66789de9df381cc16c36ca6da1 (diff) | |
download | chromium_src-4d2efd2e100bc961d3e19e0a6f242c7914917690.zip chromium_src-4d2efd2e100bc961d3e19e0a6f242c7914917690.tar.gz chromium_src-4d2efd2e100bc961d3e19e0a6f242c7914917690.tar.bz2 |
Convert the pp::proxy namespace to the ppapi::proxy namespace.
This is more consistent with the stuff in shared_impl, and removes a lot of
namespace using goop.
Add a unified resource tracker shared between the proxy and the impl.
This renames the old ResourceObjectBase to Resource and removes the old
PluginResource. It moves the resource tracker from the impl to the
shared_impl, and makes the proxy use it.
Some things become a little less neat because there's no proxy resource base
class. In particular GetDispatcher() is now gone. I considered whether to
add a helper base class that provides this function, but decided against it
and had individual resource classes implement this when their implementation
would find it useful. This is because ultimately I want more of this
functionality to move into the shared_impl, and it's easier to do that if
there are fewer proxy-specific things in the resources.
This changes the way that plugins are added to the tracker. Previously they
would only be in the tracker if the plugin had a reference to them, although
they could be alive if the impl had a scoped_ptr referencing an object. This
actually has the bug that if we then give the resource back to the plugin,
it wouldn't be refcounted properly and everything would get confused.
Now the tracker tracks all live resource objects whether or not the plugin
has a ref. This works basically like the var tracker (it would be nice if
the var and resource trackers shared more code, but that would further
complicate this already overcomplicated patch). The resource tracker takes an
extra ref whenever the plugin has one or more, and otherwise just tracks live
resources.
BUG=
TEST=
Review URL: http://codereview.chromium.org/7655002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97367 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/ppapi_plugin/plugin_process_dispatcher.cc')
-rw-r--r-- | content/ppapi_plugin/plugin_process_dispatcher.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/ppapi_plugin/plugin_process_dispatcher.cc b/content/ppapi_plugin/plugin_process_dispatcher.cc index 08528e7..0243100 100644 --- a/content/ppapi_plugin/plugin_process_dispatcher.cc +++ b/content/ppapi_plugin/plugin_process_dispatcher.cc @@ -23,7 +23,7 @@ const int kPluginReleaseTimeMs = 30 * 1000; // 30 seconds. PluginProcessDispatcher::PluginProcessDispatcher( base::ProcessHandle remote_process_handle, GetInterfaceFunc get_interface) - : pp::proxy::PluginDispatcher(remote_process_handle, get_interface) { + : ppapi::proxy::PluginDispatcher(remote_process_handle, get_interface) { ChildProcess::current()->AddRefProcess(); } |