Implement robustness strings in requestMediaKeySystemAccess().

media/base/eme_constants.h

 // Copyright 2014 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.
 
 #ifndef MEDIA_BASE_EME_CONSTANTS_H_
 #define MEDIA_BASE_EME_CONSTANTS_H_
 
 #include <stdint.h>
 
 namespace media {
@@ skipping 42 matching lines @@
   // Invalid default value.
   EME_SESSION_TYPE_INVALID,
   // The session type is not supported.
   EME_SESSION_TYPE_NOT_SUPPORTED,
   // The session type is supported if the encrypted media permission is granted.
   EME_SESSION_TYPE_SUPPORTED_WITH_PERMISSION,
   // The session type is always supported.
   EME_SESSION_TYPE_SUPPORTED,
 };
 
+// Used to declare support for distinctive identifier and persistent state.
 enum EmeFeatureSupport {
   // Invalid default value.
   EME_FEATURE_INVALID,
   // Access to the feature is not supported at all.
   EME_FEATURE_NOT_SUPPORTED,
   // Access to the feature may be requested if the encrypted media permission is
   // granted.
   EME_FEATURE_REQUESTABLE_WITH_PERMISSION,
   // Access to the feature may be requested.
   EME_FEATURE_REQUESTABLE,
   // Access to the feature cannot be blocked.
   EME_FEATURE_ALWAYS_ENABLED,
 };
 
+// Used to query support for distinctive identifier and persistent state.
 enum EmeFeatureRequirement {
   EME_FEATURE_NOT_ALLOWED,
   EME_FEATURE_OPTIONAL,
   EME_FEATURE_REQUIRED,
 };
 
+enum class EmeMediaType {
+  AUDIO,
+  VIDEO,
+};
+
+// Robustness values understood by KeySystems. Each value imples all those
+// before it. (This may need to be redesigned to support non-Widevine CDMs.)
+enum class EmeRobustness {
+  INVALID,
+  EMPTY,
+  SW_SECURE_CRYPTO,
+  SW_SECURE_DECODE,
+  HW_SECURE_CRYPTO,
+  HW_SECURE_DECODE,
+  HW_SECURE_ALL,
+};
+
+// Configuration rules are recipes for determining if a feature is supported,

[ddorwin, 2015/03/16 23:25:08]

Not really "recipes"?

[sandersd (OOO until July 31), 2015/03/17 22:10:38]

Done.

+// and for updating configuration state for evaluating later rules. They are
+// used to answer queries about distinctive identifier, persistent state, and
+// robustness support.
+enum class EmeConfigRule {

[ddorwin, 2015/03/16 23:25:08]

"Rule" doesn't seem appropriate. SupportStatus? SupportCondition?

[sandersd (OOO until July 31), 2015/03/17 22:10:38]

Condition is accurate. Let me know if it still needs to be changed now that the
comments are improved.

+  // The feature is not supported.
+  NOT_SUPPORTED,
+  // The feature is supported if the encrypted media permission is granted.
+  PERMISSION_REQUIRED,
+  // The feature is supported, but the user experience may be improved if the
+  // encrypted media permission is granted.
+  PERMISSION_RECOMMENDED,
+  // The feature is supported without conditions.
+  SUPPORTED,

[ddorwin, 2015/03/16 23:25:08]

This does not indicate whether it can be disabled. Perhaps the questions are
"does support not using" to which SUPPORTED would be returned. If so, then the
comment should probably be updated - "feature" can also be not doing something.

[sandersd (OOO until July 31), 2015/03/17 22:10:38]

Done.

+};
+
 }  // namespace media
 
 #endif  // MEDIA_BASE_EME_CONSTANTS_H_