Add mux-stream transport support in session description

remoting/protocol/name_value_map.h

+// Copyright (c) 2012 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.
+//
+// Helper functions that allow to map enum values to strings.
+
+namespace remoting {
+namespace protocol {
+
+template <typename T>
+struct NameMapElement {

[Wez, 2012/08/14 20:56:32]

nit: If you make both |value| and |name| template typed then you can make this
an A<->B map helper, which could then be re-used for things like the
native<->USB keycode lookup code.

[Sergey Ulanov, 2012/08/14 21:21:36]

We need to store char* in the static array (to avoid static
initializers/finalizers), but compare it to the string, so it's not that easy to
make it more generic.

+  const T value;
+  const char* const name;
+};
+
+template <typename T, size_t N>
+const char* ValueToName(const NameMapElement<T> (&map)[N], T value) {
+  for (size_t i = 0; i < N; ++i) {
+    if (map[i].value == value)
+      return map[i].name;
+  }
+  return NULL;
+}
+
+template <typename T, size_t N>
+bool NameToValue(const NameMapElement<T> (&map)[N],
+                 const std::string& name,
+                 T* result) {

[Wez, 2012/08/14 20:56:32]

nit: Why not return const T* and have the caller check the result for NULL?

[Sergey Ulanov, 2012/08/14 21:21:36]

I think that would be more confusing and harder to use.

+  for (size_t i = 0; i < N; ++i) {
+    if (map[i].name == name) {
+      *result = map[i].value;
+      return true;
+    }
+  }
+  return false;
+}
+
+}  // namespace protocol
+}  // namespace remoting