Make it possible to read CLD data from a file

chrome/common/render_messages.h

Index: chrome/common/render_messages.h
diff --git a/chrome/common/render_messages.h b/chrome/common/render_messages.h
index aef972780f45f16b67350ddce4eebf98663a7481..16aed372a517ee0f6874846c5f54fbf1da6dbae1 100644
--- a/chrome/common/render_messages.h
+++ b/chrome/common/render_messages.h
@@ -410,6 +410,13 @@ IPC_MESSAGE_ROUTED2(ChromeViewMsg_RetrieveMetaTagContent,
                     std::string /* tag_name */ )
 #endif  // defined(OS_ANDROID)
 
+// Informs the renderer process that Compact Language Detector (CLD) data is

[bulach, 2014/03/11 18:56:10]

probably best to keep close together with other translate messages?
also, the name could imply that, something like:
ChromeViewMsg_TranslateCLDDataAvailable, or something..

[Andrew Hayden (chromium.org), 2014/03/13 16:33:33]

Proximity: The ChromeViewMsg and ChromeViewHostMsg chunks seem to be divided
intentionally, which is why I've got them separated. Am I incorrect?

I prefer not to include the word Translate. Yes, it's true that Translate is
currently the only consumer of CLD data, but CLD is independent of Translate and
other features could conceivably want CLD capabilities in the future (admittedly
unlikely). If you feel strongly, let me know.

+// available and provides an IPC::PlatformFileForTransit obtained from
+// IPC::GetFileHandleForProcess(...)
+// See also: ChromeViewHostMsg_NeedCLDData
+IPC_MESSAGE_ROUTED1(ChromeViewMsg_CLDDataAvailable,
+                    IPC::PlatformFileForTransit)
+
 // chrome.principals messages ------------------------------------------------
 
 // Message sent from the renderer to the browser to get the list of browser
@@ -771,3 +778,10 @@ IPC_MESSAGE_ROUTED4(ChromeViewHostMsg_DetailedConsoleMessageAdded,
                     base::string16 /* source */,
                     extensions::StackTrace /* stack trace */,
                     int32 /* severity level */)
+
+// Informs the browser process that Compact Language Detector (CLD) data is

[bulach, 2014/03/11 18:56:10]

ditto

[Andrew Hayden (chromium.org), 2014/03/13 16:33:33]

See other response.

+// required by the originating renderer. The browser process should respond
+// with a ChromeViewMsg_CLDDataAvailable if the data is available, else it
+// should go unanswered (the renderer will ask again later)
+// See also: ChromeViewMsg_CLDDataAvailable
+IPC_MESSAGE_ROUTED0(ChromeViewHostMsg_NeedCLDData)