- From: mwatson2 <web-platform-tests-notifications@w3.org>
- Date: Thu, 15 Sep 2016 18:29:53 GMT
- To: public-web-platform-tests-notifications@w3.org
We can use the rental profiles to test the expiration attribute, if we want to. On Thu, Sep 15, 2016 at 11:10 AM, jdsmith3000 <notifications@github.com> wrote: > LGTM. Settings disable default output link protection. Here are some > server details: > > Purchase/Rental Profile (userId) > purchase .. Purchase profile > rental1 .. Rental profile (Expires after 10min) > rental2 .. Rental profile (Expires after 1min) > rental3 .. Rental profile (playDuration 5min, purchaseDuration 10min) > For both rental profiles, absoluteExpiration is set to current date + > expiry and playDuration is set to expiry. > > Output Protection (sessionId) > a[0|1] ... analogue output protection > d[0|1] ... digital output protection > f[0|1] ... output protection enforce (0..best effort) > p[0|1] ... persistent license > default == a1d1f0p1 > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/web-platform-tests/pull/3733#issuecomment-247406147>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AHPfizhH5eQzgaFSlocYiaHZHQuxNB9Wks5qqYokgaJpZM4J-JBj> > . > View on GitHub: https://github.com/w3c/web-platform-tests/pull/3733#issuecomment-247411412
Received on Thursday, 15 September 2016 18:30:00 UTC