net: Add NET_API to a few more files.

net/proxy/dhcp_proxy_script_fetcher_factory.h

Index: net/proxy/dhcp_proxy_script_fetcher_factory.h
===================================================================
--- net/proxy/dhcp_proxy_script_fetcher_factory.h	(revision 85994)
+++ net/proxy/dhcp_proxy_script_fetcher_factory.h	(working copy)
@@ -9,6 +9,7 @@
 #include "base/basictypes.h"
 #include "base/memory/singleton.h"
 #include "net/base/completion_callback.h"
+#include "net/base/net_api.h"
 #include "net/url_request/url_request_context.h"
 
 namespace net {
@@ -29,7 +30,7 @@
 //
 // Therefore, we have platform-specific implementations, and so we use
 // this factory to select the right one.
-class DhcpProxyScriptFetcherFactory {
+class NET_API DhcpProxyScriptFetcherFactory {

[wtc, 2011/05/20 22:21:19]

I am surprised that DhcpProxyScriptFetcherFactory needs to
be exposed to the user of our network stack.  This is a sign
that we leak too many implementation details.

Is this used by the IOThread to set up the various
URLRequestContext objects?

[rvargas (doing something else), 2011/05/20 22:54:55]

chrome/browser/net/connection_tester.cc and
chrome/browser/net/proxy_service_factory.cc use it to setup the proxy service.

On 2011/05/20 22:21:19, wtc wrote:

  public:
   // Creates a new factory object with default settings.
   DhcpProxyScriptFetcherFactory();