Establish the content/components directory.

content/components/README

+This directory is for components that have the Content Module as the
+uppermost layer they depend on.  They may depend only on the Content
+API (content/public) and on lower layers (e.g. base/, net/, ipc/
+etc.).
+
+These components are not part of the Content Module itself.  They are
+built in a separate .gyp file (content_components.gyp in this
+directory).
+
+Components that have bits of code that need to live in different
+processes (e.g. some code in the browser process, some in the renderer
+process, etc.) should separate the code into different subdirectories.
+Hence for a component named 'foo' you might end up with a structure
+like the following:
+
+content/components/foo - DEPS, OWNERS, foo.gypi
+content/components/foo/browser - code that needs the browser process
+content/components/foo/common - for e.g. IPC constants and such
+content/components/foo/renderer - code that needs renderer process
+content/components/foo/java - Android code

[darin (slow to review), 2012/10/30 18:18:25]

One of these is not like the others.  Why is java a peer to browser, common and
renderer?  It seems like java code could be browser-side only, renderer-side
only, or used in both.

+
+These subdirectories should have DEPS files with the relevant
+restrictions in place, e.g. only content/components/foo/browser should
+be allowed to #include from content/public/browser.

[John Knottenbelt, 2012/10/30 18:48:29]

Please could you add a statement on what C++ namespace is to be used for
components?