summaryrefslogtreecommitdiffstats
path: root/net/dns
Commit message (Collapse)AuthorAgeFilesLines
* HostResolver: don't interpret NULL callback argument as a request to do ↵agayev@chromium.org2011-08-043-63/+68
| | | | | | | | | | | synchronous resolution. BUG=90547,60149 TEST=net_unittests Review URL: http://codereview.chromium.org/7492059 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95509 0039d316-1c4b-4281-b951-d872f2087c98
* AsyncHostResolver refactoring.agayev@chromium.org2011-07-263-113/+143
| | | | | | | | | | | This change gets rid of the asymmetry between Resolve() calls that complete synchronously and those that complete asynchronously. Makes code more readable/understandable, allows to embed OnStart/OnFinish/OnCancel calls within the Request::Request()/Request::On{Sync,Async}Complete/Request::~Request() so that we do not miss these inadvertently. As a result of this, I found out that code logic as well as the unit test was not notifying the observer of the cancellation due to object destruction. BUG=60149 TEST=net_unittests --gtest_filter="AsyncHostResolverTest*" Review URL: http://codereview.chromium.org/7492028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94133 0039d316-1c4b-4281-b951-d872f2087c98
* File reorganization: move AsyncHostResolver files to net/dns.agayev@chromium.org2011-07-2214-0/+2899
BUG=60149 TEST=net_unittest --gtest_filter="AsyncHostResolver*" Review URL: http://codereview.chromium.org/7484012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93644 0039d316-1c4b-4281-b951-d872f2087c98