chromium_src.git - central chromium sources

	Commit message (Collapse)	Author	Age	Files	Lines
*	Don't use the AI_ADDRCONFIG flag on Mac OS X. It's not necessary.	wtc@chromium.org	2009-08-17	1	-0/+17
\| \| \| \| \| \| \| \| \| \| \|	Hopefully this will fix issue 12711. R=eroman,mark BUG=http://crbug.com/12711 TEST=covered by existing unit tests and normal browsing on Mac Review URL: http://codereview.chromium.org/172061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23590 0039d316-1c4b-4281-b951-d872f2087c98
*	Undisable HostResolverImplTest.EmptyHost, by making empty host fail to resolve.	ericroman@google.com	2009-08-17	1	-0/+6
\| \| \| \| \| \|	Review URL: http://codereview.chromium.org/164546 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23576 0039d316-1c4b-4281-b951-d872f2087c98
*	Refactorings surrounding HostResolver:	ericroman@google.com	2009-07-15	1	-0/+180
	(1) Extract HostResolver to an interface. The existing concrete implementation is now named HostResolverImpl. This makes it possible to create mocks with more complex behavior (i.e. choose via rules if response will be sync vs async). (2) Transform HostMapper into HostResolverProc. Conceptually HostResolverProc maps a hostname to a socket address, whereas HostMapper mapped a hostname to another hostname (so you were still at the mercy of the system's host resolver). With HostResolverProc you can specify the exact AddressList, making it possible to run tests requiring IPv6 socketaddrs on systems (like WinXP) that don't actually support it. (3) Add a MockHostResolver implementation of HostResolver. This replaces the [ScopedHostMapper + RuleBasedHostMapper + HostResolver] combo. It is less clunky and a bit more expressive. BUG=http://crbug.com/16452 R=willchan TEST=existing Review URL: http://codereview.chromium.org/149511 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20795 0039d316-1c4b-4281-b951-d872f2087c98