Initial implementation of Chrome Early Loading Framework

chrome_elf/README

Index: chrome_elf/README
diff --git a/chrome_elf/README b/chrome_elf/README
new file mode 100644
index 0000000000000000000000000000000000000000..89bb1db8c7f9dccbd3aed77e85222127f328af11
--- /dev/null
+++ b/chrome_elf/README
@@ -0,0 +1,21 @@
+Chrome Early Loading Framework (aka ChromeELF)
+
+chrome_elf.dll is shipped in Chrome's version directory to ease updates,
+and is loaded early in chrome.exe's lifetime. This is done by making it a
+private assembly in a subfolder of chrome.exe's folder (see
+http://msdn.microsoft.com/library/aa374224.aspx).
+
+In an ideal world, this would be done by embedding an application config in
+chrome.exe that would refer to the proper version directory via a
+probing\privatePath attribute (http://msdn.microsoft.com/library/aa374182.aspx).
+This would allow us to refer to dlls in the version directory without having to
+make the version directory itself into an assembly. Unfortunately, this
+method is only supported for Windows 7 and later.
+
+Instead, we use "Assembly Searching Sequence"
+(http://msdn.microsoft.com/library/aa374224.aspx) which states that private
+assemblies can be placed in a subfolder if that subfolder has the same name as
+the assembly itself, and treat the version directory as a private assembly.
+
+This is the best way to have chrome.exe find chrome_elf.dll at load-time without
+putting it beside chrome.exe in the application directory.