AllowBroadcast() is exposed to NaCl.

ppapi/api/private/ppb_udp_socket_private.idl

Index: ppapi/api/private/ppb_udp_socket_private.idl
diff --git a/ppapi/api/private/ppb_udp_socket_private.idl b/ppapi/api/private/ppb_udp_socket_private.idl
index 083c33d1991a31f8b41ffd978b3b2d2425f238cc..a72aaa1ba745b8a46897e5f0c1e72eeac12b95a9 100644
--- a/ppapi/api/private/ppb_udp_socket_private.idl
+++ b/ppapi/api/private/ppb_udp_socket_private.idl
@@ -9,7 +9,24 @@
 
 label Chrome {
   M17 = 0.2,
-  M19 = 0.3
+  M19 = 0.3,
+  M23 = 0.4
+};
+
+[assert_size(4)]
+enum PP_UDPSocketFeature_Private {
+  // Allow the socket to share the local address to which socket will
+  // be bound with other processes. Value's type should be
+  // PP_VARTYPE_BOOL.
+  PP_UDPSOCKETFEATURE_ADDRESS_REUSE = 0,
+
+  // Allow sending and receiving packets sent to and from broadcast
+  // addresses. Value's type should be PP_VARTYPE_BOOL.
+  PP_UDPSOCKETFEATURE_BROADCAST = 1,
+
+  // Special value for counting the number of available
+  // features. Should not be passed to SetSocketFeature().
+  PP_UDPSOCKETFEATURE_COUNT = 2
 };
 
 interface PPB_UDPSocket_Private {
@@ -23,6 +40,12 @@ interface PPB_UDPSocket_Private {
    */
   PP_Bool IsUDPSocket([in] PP_Resource resource_id);
 
+  [version=0.4]

[brettw, 2012/08/20 04:34:45]

Can you provide documentation for this? In particular, what the callback means.
Does it mean the setting has taken effect? Do we really need the callback?
Normally these "set the setting" things don't need one. And it's also weird that
you can only set one setting at once (you could easily imagine wanting to set
several options on the socket).

[ygorshenin1, 2012/08/20 12:08:01]

Done.

Yes, callback means that the setting has effect. SetSocketFeature takes PP_Var
as value and callback so it's very general and can be easily extended. If some
complex check will be performed on the browser side, callback will be the only
way to pass back results.

I agree, that set once setting at once is weird, but in this case we can easily
verify compatibility of feature name and value type (and value). Also POSIX and
WS2 setsockopt takes option name, not or-ed combination of names.

On 2012/08/20 04:34:45, brettw wrote:

[brettw, 2012/08/20 17:55:15]

My weird that you can't set more than one at a time, I wasn't referring to
bitwise or-ing things, but rather that if you want to set two options, you have
to write a complex state machine since you can't set the second one until the
callback for the first one completes.

I don't think we should design this based on potential future extensibility. We
can always add a separate function or a new option setting function if we start
adding fancy checks that require callbacks.

[ygorshenin1, 2012/08/21 12:00:27]

OK, I'll delete callbacks.

On 2012/08/20 17:55:15, brettw wrote:

+  int32_t SetSocketFeature([in] PP_Resource udp_socket,
+                           [in] PP_UDPSocketFeature_Private name,
+                           [in] PP_Var value,
+                           [in] PP_CompletionCallback callback);
+
   /* Creates a socket and binds to the address given by |addr|. */
   int32_t Bind([in] PP_Resource udp_socket,
                [in] PP_NetAddress_Private addr,