Chromium Code Reviews| Index: remoting/base/scoped_thread_proxy.h |
| diff --git a/remoting/base/scoped_thread_proxy.h b/remoting/base/scoped_thread_proxy.h |
| index 2ec9b5b69b1fe8cb650e7a2b163867dbcd53ccc7..3638ef160fcc42d3a2590ba4bd96c9a489835f5f 100644 |
| --- a/remoting/base/scoped_thread_proxy.h |
| +++ b/remoting/base/scoped_thread_proxy.h |
| @@ -15,9 +15,6 @@ namespace remoting { |
| // for a non-refcounted object. Must be deleted on the thread it |
| // belongs to. |
| // |
| -// The main difference from WeakPtr<> and ScopedRunnableMethodFactory<> |
|
Sergey Ulanov
2012/01/03 18:49:00
This comment is still useful to explain why WeakPt
James Hawkins
2012/01/03 21:13:54
Done.
|
| -// is that this class can be used safely to post tasks from different |
| -// threads. |
| // It is similar to WeakHandle<> used in sync: the main difference is |
| // that WeakHandle<> creates closures itself, while ScopedThreadProxy |
| // accepts base::Closure instances which caller needs to create using |