Chromium Code Reviews| Index: chrome/browser/storage_monitor/storage_monitor.h |
| diff --git a/chrome/browser/storage_monitor/storage_monitor.h b/chrome/browser/storage_monitor/storage_monitor.h |
| index 7eab0b7743b925d9b3fffa009623e946c32b496d..d57f43c84a94bb0ae8e6de9cc5c8a8fb0e30412e 100644 |
| --- a/chrome/browser/storage_monitor/storage_monitor.h |
| +++ b/chrome/browser/storage_monitor/storage_monitor.h |
| @@ -73,6 +73,11 @@ class StorageMonitor { |
| // Should be invoked on the UI thread; callbacks will be run on the UI thread. |
| void Initialize(base::Closure callback); |
| + // Register a callback to be called when the initialization is completed. If |
| + // the initialization is already completed, the provided callback will be |
| + // invoked with the calling stack. |
| + void RegisterInitCompletedCallback(base::Closure callback); |
|
vandebo (ex-Chrome)
2013/05/28 20:00:29
This is the same as Initialize - remove.
Hongbo Min
2013/05/29 01:05:38
No, from the source code of Initialize, it will in
|
| + |
| // Return true if the storage monitor has already been initialized. |
| bool IsInitialized(); |
| @@ -102,6 +107,11 @@ class StorageMonitor { |
| media_transfer_protocol_manager() = 0; |
| #endif |
| + // Returns the meta information for all available storages on the system, |
|
vandebo (ex-Chrome)
2013/05/28 20:00:29
This change should be done as a separate CL.
Hongbo Min
2013/05/29 01:05:38
OK. I will do that in a separate CL.
|
| + // including fixed and removable storage. It may return an empty vector |
| + // if the storage metadata retrieval is not completed yet on FILE thread. |
| + virtual std::vector<StorageInfo> GetAllAvailableStorages() const; |
| + |
| // Returns information for attached removable storage. |
| std::vector<StorageInfo> GetAttachedStorage() const; |