DescriptionRefactor ProcessSingleton so that it may be used distinctly from a full browser process.
The main effect is that ProcessSingleton is much more restricted to its basic functionality, which is to ensure that a single instance of Chrome runs per profile directory and to pass messages from new Chrome invocations to the existing instance.
Exactly how those messages were handled has been moved from the implementations of ProcessSingleton into ChromeBrowserMain where (I think) it more rightly belongs.
This will allow the Chrome Frame net tests to use ProcessSingleton to implement a stub Chrome for the purpose of handling network-related IPC from Chrome Frame without having to launch the rest of Chrome, upon which ProcessSingleton previously depended directly.
BUG=None
TEST=None
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=130853
Patch Set 1 #Patch Set 2 : Fix a call to ProcessCommandLine #Patch Set 3 : Move callback declaration out of windows ifdef. #Patch Set 4 : Fix build break on Linux. #Patch Set 5 : Fix mac build breakage. #Patch Set 6 : Mac unit-test fixage. #Patch Set 7 : Linux unit-test fixage. #Patch Set 8 : Further linux test compilation fixage. #Patch Set 9 : Merge master. #Patch Set 10 : Include cleanup. #
Total comments: 9
Patch Set 11 : Remove legacy code that doesn't need to survive this refactoring. Fix a comment. #Patch Set 12 : Fix comment nits. #
Messages
Total messages: 18 (0 generated)
|