Add DISABLE_TCP_TRANSPORT flag in the Transport API.

ppapi/c/dev/ppb_transport_dev.h

Index: ppapi/c/dev/ppb_transport_dev.h
diff --git a/ppapi/c/dev/ppb_transport_dev.h b/ppapi/c/dev/ppb_transport_dev.h
index fb1513ef690f52bcbdfc41a5a2af18ad877ff41a..244cda0a8b9d2e2ad346dec3df8762f8e891dbfb 100644
--- a/ppapi/c/dev/ppb_transport_dev.h
+++ b/ppapi/c/dev/ppb_transport_dev.h
@@ -48,7 +48,11 @@ typedef enum {
   PP_TRANSPORTPROPERTY_TCP_NO_DELAY = 7,
 
   // Delay for ACK packets in milliseconds. By default set to 100ms.
-  PP_TRANSPORTPROPERTY_TCP_ACK_DELAY = 8
+  PP_TRANSPORTPROPERTY_TCP_ACK_DELAY = 8,
+
+  // Types of ports to use. An integer that is a bit-mast of
+  // PP_TransportPorts values. By default all ports are disabled.

[Wez, 2011/09/13 19:57:19]

It might be better to use the term "protocols" rather than "ports", since the
term "port" relates to the internals of libjingle, whereas what matters to the
caller is the protocols used.

Does it make sense for all ports to be disabled?

[Sergey Ulanov, 2011/09/13 20:31:38]

Ok, I'll change it to protocol.
That was a typo in the comment. By default all are enabled.

+  PP_TRANSPORTPROPERTY_PORT_TYPES = 9
 } PP_TransportProperty;
 PP_COMPILE_ASSERT_SIZE_IN_BYTES(PP_TransportProperty, 4);
 
@@ -60,6 +64,17 @@ typedef enum {
   PP_TRANSPORTRELAYMODE_GOOGLE = 1
 } PP_TransportRelayMode;
 
+typedef enum {
+  PP_TRANSPORTPORTS_UDP = 1 << 0,
+  PP_TRANSPORTPORTS_TCP = 1 << 1,
+  PP_TRANSPORTPORTS_STUN = 1 << 2,
+  PP_TRANSPORTPORTS_RELAY_UDP = 1 << 3,
+  PP_TRANSPORTPORTS_RELAY_TCP = 1 << 4,
+  PP_TRANSPORTPORTS_RELAY_SSLTCP = 1 << 5,

[Wez, 2011/09/13 19:57:19]

Are we ever likely to want to add more of these, e.g. UDP4 to force IPv4 UDP
once IPv6 is available?

If so then splitting them into blocks might be better, e.g. UDP & TCP in the
lower 16-bits of "direct" types, STUN in an 8-bit block of nat-traversing types,
and the RELAY options in a final 8-bit block of relay types.

[Sergey Ulanov, 2011/09/13 20:31:38]

It's probable that we may want to add more protocols in the future, but I don't
think there is a valid reason to distinguish IPv4 and IPv6 ports, so I don't
think it's worth splitting these in blocks, as we don't know what kind of
protocols we will want to add in the future.

+
+  PP_TRANSPORTPORTS_ALL = 0xFFFFFFFF
+} PP_TransportPorts;
+
 struct PPB_Transport_Dev {
   // Creates a new transport object with the specified name using the
   // specified protocol.