Add SetProperty() in the PPB_Transport_Dev interface.

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 bc3a8cd44075eddb344fdcffa8906a2fffb46563..a90ba03b24b9f838707d52297ea47db73a6ea10f 100644
--- a/ppapi/c/dev/ppb_transport_dev.h
+++ b/ppapi/c/dev/ppb_transport_dev.h
@@ -34,6 +34,10 @@ struct PPB_Transport_Dev {
   // connect type, protocol
   // RTT
 
+  // Set STUN/relay server configuration, as well as other
+  // configuration parameters.

[brettw, 2011/08/22 23:59:59]

This documentation gives me no idea what I can pass in config. Can this be
significantly expanded or can you give a pointer to where I can figure this out?
(Maybe a simple example would also be nice.)

Actually, I think I'd prefer something more like the URLRequestInfo where you
have an enum of all the supported options, and then set them individually. I
think this makes the calling code more clear, and it also makes it easier to
tell what options we support. The parameter can be a var so you can pass
integers for things like the receive window and not have to do parsing.

[Sergey Ulanov, 2011/08/23 19:02:04]

I like the idea of SetProperty() and enum with all properties. One problem I see
with this approach is that array support is not yet implemented in PP_Var, and
it would be useful here for specifying stun and relay server addresses. For now
I think I can use comma-separated lists for these parameters, and switch to
arrays later when they are implemented. What do you think about it?

How hard would it be to implement array vars?

+  int32_t (*SetConfig)(PP_Resource transport, const char* config);
+
   // Establishes a connection to the remote peer.  Returns
   // PP_OK_COMPLETIONPENDING and notifies on |cb| when connectivity is
   // established (or timeout occurs).