Mojo UDP socket API definition.

mojo/services/public/interfaces/network/net_address.mojom

Index: mojo/services/public/interfaces/network/net_address.mojom
diff --git a/mojo/services/public/interfaces/network/net_address.mojom b/mojo/services/public/interfaces/network/net_address.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..82da48bf2f5f31cf922cb9b0a1ada89713c2a29a
--- /dev/null
+++ b/mojo/services/public/interfaces/network/net_address.mojom
@@ -0,0 +1,32 @@
+// Copyright 2014 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.
+
+module mojo {
+
+enum NetAddressFamily {
+  UNSPECIFIED,
+  IPV4,
+  IPV6
+};
+
+// All members are expressed in network byte order.

[brettw, 2014/09/29 17:49:16]

Can you expand on this or give an example. Some users won't know what this
means.

[yzshen1, 2014/09/29 19:32:35]

Done.

+struct NetAddressIPv4 {
+  uint16 port;
+  uint8[4] addr;
+};
+
+// All members are expressed in network byte order.
+struct NetAddressIPv6 {
+  uint16 port;
+  uint8[16] addr;
+};
+
+struct NetAddress {
+  NetAddressFamily family = UNSPECIFIED;
+  NetAddressIPv4? ipv4;

[yzshen1, 2014/09/22 19:44:48]

This approach has the disadvantage that whenever we add a new address type, we
will have another pointer and waste 8 more bytes. (Do we want union support?)

Another approach is to have a uint8 array here. And then the user can use our
binding helpers to Deserialize() it into NetAddressIPv4 or NetAddressIPv6,
depending on the address type.

Which do you prefer? Thanks!

[brettw, 2014/09/29 17:41:22]

I like the way you did it better, but it seems like there should be some
comments here explaining that only one is valid depending on the "family"

[yzshen1, 2014/09/29 19:32:35]

Done.

+  NetAddressIPv6? ipv6;
+};
+
+}
+