| Index: remoting/client/plugin/pepper_view.h
|
| diff --git a/remoting/client/plugin/pepper_view.h b/remoting/client/plugin/pepper_view.h
|
| index 1213533cb682917069a1736438bf10eb047c3fea..0b49a565d7d1bbad67dc89f9d459131898c4be02 100644
|
| --- a/remoting/client/plugin/pepper_view.h
|
| +++ b/remoting/client/plugin/pepper_view.h
|
| @@ -3,13 +3,9 @@
|
| // found in the LICENSE file.
|
|
|
| // This class is an implementation of the ChromotingView using Pepper devices
|
| -// as the backing stores. The public APIs to this class are thread-safe.
|
| -// Calls will dispatch any interaction with the pepper API onto the pepper
|
| -// main thread.
|
| -//
|
| -// TODO(ajwong): We need to better understand the threading semantics of this
|
| -// class. Currently, we're just going to always run everything on the pepper
|
| -// main thread. Is this smart?
|
| +// as the backing stores. This class is used only on pepper thread.
|
| +// Chromoting objects access this object through PepperViewProxy which
|
| +// delegates method calls on the pepper thread.
|
|
|
| #ifndef REMOTING_CLIENT_PLUGIN_PEPPER_VIEW_H_
|
| #define REMOTING_CLIENT_PLUGIN_PEPPER_VIEW_H_
|
|
|