- From: xhwang-chromium via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Jan 2017 22:28:37 +0000
- To: public-html-media@w3.org
xhwang-chromium has just created a new issue for https://github.com/w3c/encrypted-media: == Unclear text about application managing storage generated by CDM == In the current spec on [persistent-license](https://w3c.github.io/encrypted-media/#dom-mediakeysessiontype-persistent-license), it says: > The session must be loadable via its Session ID once update() is called successfully. **The application is responsible for managing any such storage that may be generated by the CDM.** See Session Storage and Persistence. It's not clear to me what "such storage" generated by the CDM the application is responsible for managing. After some offline discussion (with ddorwin@), this is really about the text appeared at the end of [6.6 Session Storage and Persistence](https://w3c.github.io/encrypted-media/#session-storage): > An application that creates a session using a persistent-license should later remove the stored data using remove(). The CDM may also remove sessions as appropriate, but applications should not rely on this. However, it's pretty hard to figure this out from the current text. We should clarify this part to avoid any future confusion. Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/369 using your GitHub account
Received on Tuesday, 24 January 2017 22:28:43 UTC