- From: Peter Beverloo <notifications@github.com>
- Date: Wed, 20 Jan 2016 13:52:28 -0800
- To: w3c/push-api <push-api@noreply.github.com>
Received on Wednesday, 20 January 2016 21:53:00 UTC
LGTM I prefer using a BufferSource because (a) the UA generally won't have to do anything with the key, and (b) there is no ubiquitous support for uncompressed EC points across Web Crypto implementations. I'm guessing that the common case will become something like: ```javascript const APPLICATION_SERVER_KEY = new Uint8Array([ 0x04, 0x00, 0x00, 0x00, ... ]); ``` Which is much more developer friendly than loading a CryptoKey object (which, in Chrome, requires converting to a JWK object prior to importing :-/). Thank you! :) --- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/pull/182#issuecomment-173372530
Received on Wednesday, 20 January 2016 21:53:00 UTC