Start splitting out WebUI into an implementation class and an interface that each page implements...

chrome/browser/ui/webui/net_internals/net_internals_ui.cc

Index: chrome/browser/ui/webui/net_internals/net_internals_ui.cc
===================================================================
--- chrome/browser/ui/webui/net_internals/net_internals_ui.cc	(revision 117388)
+++ chrome/browser/ui/webui/net_internals/net_internals_ui.cc	(working copy)
@@ -1637,7 +1637,7 @@
   return constants_dict;
 }
 
-NetInternalsUI::NetInternalsUI(WebContents* contents) : WebUI(contents) {
+NetInternalsUI::NetInternalsUI(WebContents* contents) : WebUI(contents, this) {

[eroman, 2012/01/13 00:35:38]

I imagine this setup is just transitional while refactoring?

In particular I am a bit weary of passing the |this| pointer down to the base
class. This can be a risky pattern since destruction happens in reverse order,
and if the base class's destructor were to call virtual methods on this pointer
the results can be unexpected.

Still LGTM, but please be aware of this limitation.

[jam, 2012/01/13 00:39:51]

yep this is definitely transitional, so i don't send a huge patch out for review
:)

   AddMessageHandler(new NetInternalsMessageHandler());
 
   // Set up the chrome://net-internals/ source.