SyncSocket Transit Descriptor - refactoring

base/sync_socket_nacl.cc

Index: base/sync_socket_nacl.cc
diff --git a/base/sync_socket_nacl.cc b/base/sync_socket_nacl.cc
index f6d17e7ffb61dc20468bbd4e987c927171273f11..a0e3ea9ef426572d28892be9929d8cc247e3dc96 100644
--- a/base/sync_socket_nacl.cc
+++ b/base/sync_socket_nacl.cc
@@ -27,6 +27,24 @@ bool SyncSocket::CreatePair(SyncSocket* socket_a, SyncSocket* socket_b) {
   return false;
 }
 
+// static
+SyncSocket::Handle SyncSocket::UnwrapHandle(
+    const SyncSocket::TransitDescriptor& descriptor) {
+  // TODO(burnik): Still unclear how NaCl uses SyncSocket.

[henrika (OOO until Aug 14), 2014/09/02 07:46:05]

Nit, not sure if you should add put it on xians instead. Just don't want it to
be hanging when you leave.

[burnik, 2014/09/02 10:02:54]

If Shijing agrees, I will make it so.
On 2014/09/02 07:46:05, henrika wrote:

+  // See http://crbug.com/409656
+  NOTIMPLEMENTED();

[tommi (sloooow) - chröme, 2014/09/04 11:34:09]

what platforms will this run on?

[burnik, 2014/09/06 18:17:09]

NOTIMPLEMENTED is used in the rest of this NaCl SyncSocket so it should be safe
to use it here. It should run in any NaCl env. Point is that a test should fail
on this code once someone starts using it. Looks to me like a lot of SyncSocket
methods on NaCl are yet to be implemented here.

On 2014/09/04 11:34:09, tommi wrote:

+  return SyncSocket::kInvalidHandle;
+}
+
+bool SyncSocket::PrepareTransitDescriptor(
+    ProcessHandle peer_process_handle,
+    SyncSocket::TransitDescriptor* descriptor) {
+  // TODO(burnik): Still unclear how NaCl uses SyncSocket.
+  // See http://crbug.com/409656
+  NOTIMPLEMENTED();
+  return false;
+}
+
 bool SyncSocket::Close() {
   if (handle_ != kInvalidHandle) {
     if (close(handle_) < 0)