diff options
| author | kinuko@chromium.org <kinuko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-11-30 18:58:13 +0000 |
|---|---|---|
| committer | kinuko@chromium.org <kinuko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-11-30 18:58:13 +0000 |
| commit | 103c8d4b8d27edf535d8a3e7836fd1bffba28bfc (patch) | |
| tree | 343fe70815e83ca913ce3f6c5bd9bdec123a56ff /media | |
| parent | 91abc359dcbbd46f7793338d36d51dfd8629b571 (diff) | |
| download | chromium_src-103c8d4b8d27edf535d8a3e7836fd1bffba28bfc.zip chromium_src-103c8d4b8d27edf535d8a3e7836fd1bffba28bfc.tar.gz chromium_src-103c8d4b8d27edf535d8a3e7836fd1bffba28bfc.tar.bz2 | |
Make FileSystemOperation's lifetime more explicit.
In the current code calling dispatcher->DidXxx in an operation's DidXxx method MAY indirectly delete the operation itself depending on the dispatcher's implementation. I was confused by this several times and I want to make this flow more explicit.
This patch lets FileSystemOperation control its lifetime by itself so that each callback dispatcher implementation does not need to take care of it.
Also moved BrowserFileSystemCallbackDispatcher into file_system_dispatcher_host.cc as it's only used in it and its implementation is tightly coupled with the DispatcherHost.
BUG=60243
TEST=none
Review URL: http://codereview.chromium.org/4821005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67732 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media')
0 files changed, 0 insertions, 0 deletions