Put history insertion for downloads processing inline.

chrome/browser/download/download_manager.h

Index: chrome/browser/download/download_manager.h
diff --git a/chrome/browser/download/download_manager.h b/chrome/browser/download/download_manager.h
index 4f5ebcfb1cbcb6722f35c05b30642787927fb08e..43b1049fd5898d873a562672aa363f3a658ce5fc 100644
--- a/chrome/browser/download/download_manager.h
+++ b/chrome/browser/download/download_manager.h
@@ -125,6 +125,12 @@ class DownloadManager
   void PauseDownload(int32 download_id, bool pause);
   void RemoveDownload(int64 download_handle);
 
+  // Complete the non-racing portion of the download after
+  // all UI initialization had occurred and all data has
+  // arrived.  Called from locations where it is possible
+  // those conditions may apply.
+  void MaybeCompleteDownload(int32 download_id, int64 size);

[Paweł Hajdan Jr., 2011/01/03 09:43:03]

Can we find a more descriptive name, i.e. one that describes what this method
does, not when it is called?

[Randy Smith (Not in Mondays), 2011/01/04 19:29:21]

Hmmm.  My call would be that MaybeCompleteDownload actually does describe what
the call does.  Based on a certain set of conditions it may or may not complete
the download.  But I think your concern applies well to the comment, and I've
tried to update the comment to reflect that concern.  Let me know what you
think.

+
   // Called when the download is renamed to its final name.
   void DownloadRenamedToFinalName(int download_id, const FilePath& full_path);