HostResolver supports optional CNAME lookups.

net/base/address_family.h

Index: net/base/address_family.h
diff --git a/net/base/address_family.h b/net/base/address_family.h
index 065927f89ead837b6b6ac49b30d73a98f7ddfd9e..fee0584b75a295d19e9111e1a6d72a1b94af2280 100644
--- a/net/base/address_family.h
+++ b/net/base/address_family.h
@@ -1,4 +1,4 @@
-// Copyright (c) 2009 The Chromium Authors. All rights reserved.
+// Copyright (c) 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
@@ -15,6 +15,13 @@ enum AddressFamily {
   ADDRESS_FAMILY_IPV6,          // AF_INET6
 };
 
-}  // namesapce net
+// HostResolverFlags is a bitflag enum wrapper around the addrinfo.ai_flags
+// supported by host resolver procedures.
+enum {
+  HOST_RESOLVER_CANONNAME = 1 << 0,  // 0x1, AI_CANONNAME
+};
+typedef int HostResolverFlags;

[willchan no longer on Chromium, 2010/04/07 20:29:03]

Why is HostResolverFlags in address_family.h?  Why not put this in
host_resolver.h?  Is it only ever used with HostResolver?  If so, I'd expect it
be be something like

enum Flags {
  NONE = 0,
  CANONNAME = 1 << 0,
};

scoped within HostResolver.

That's assuming it's only used within HostResolver.  I haven't read through the
whole changelist to ascertain this.

[cbentzel, 2010/04/07 20:41:06]

Circular references - this is also used by HostCache (as part of the Key
structure) and HostResolverProc (where it is ultimately turned into
AI_ADDRINFO).

I originally called it AddressFlags.

+
+}  // namespace net
 
 #endif  // NET_BASE_ADDRESS_FAMILY_H_