![]() The client application can now determine what features the specific OEM implementation of the PlayReady Device Porting Kit has implemented. See "Changes in PlayReady Device Porting Kit Version 4.4" below for the corresponding benefits of this feature.Ĭhanges in PlayReady Device Porting Kit Version 4.4 General Otherwise, setting the property to true will cause the server to perform one additional asymmetric encrypt operation when generating the license acquisition response and include an "Optimized Content Key 2" in each non-leaf license included in the response.For example, if the client is older than version 4.4, the property is ignored. ![]() If the Optimized Content Key 2 feature cannot improve performance on the client, the property has no effect.Property LicenseResponse.IncludeOptimizedContentKey2 has been added (defaulting to false). For more information, see How to Determine What Features a Client Supports. For more information, see PlayReady Secure Stop.Ī server application can now determine what features the client has implemented if the client is also version 4.4 or higher. The server can now process SecureStop2 messages. Additionally, the PlayReady license server extends CBCS support for SL2000. Windows now supports CBCS for both hardware and software DRM. General changes in PlayReady Server SDK Version 4.4 When multiple non-leaf licenses are acquired in a single license acquisition response, the server can optionally perform additional cryptography to reduce cryptography on the client. The ability to determine what features a given Porting Kit implementation supports is added on both client and server. This page contains an overview of the most significant changes between PlayReady version 4.3 and PlayReady version 4.4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |