Re: Use-case for consideration, which will be difficult post-NPAPI

I would look over the discussion in https://bugzilla.mozilla.org/show_bug.cgi?id=988781 regarding future SC support via the WebCrypto JS APIs. I would hope that having a W3C spec for a smartcard API would encourage a common, cross-browser way to do this without plugins or addons. /a On

RE: Use-case for consideration, which will be difficult post-NPAPI

target, but thanks for the idea. Regards, Alex From: Adam Roach [mailto:a...@mozilla.com] Sent: 26 June 2015 07:05 To: James May; Alex Taylor Cc: dev-platform@lists.mozilla.org Subject: Re: Use-case for consideration, which will be difficult post-NPAPI I would look over the discussion in https

Re: Use-case for consideration, which will be difficult post-NPAPI

Have you considered using a local web server? That way you can use any native code you want, and it's a reasonably common approach. On many platforms you can even use socket activation to avoid the need for a always running server process. On 25 June 2015 at 21:04, Alex Taylor

Use-case for consideration, which will be difficult post-NPAPI

Good morning. I have a use-case which will be difficult to reproduce in the post-NPAPI world: The use-case is a Java/NPAPI applet which uses the javax.smartcardio library to communicate with USB-connected contactless smartcard readers, from a web-page. Extremely useful functionality for our