How does this differ from window.postMessage? I thought postMessage was going to be the main way that we did cross-origin communication between apps and service workers?
The fxos security team has been discussing ideas for how crypto-hardware (e.g. secure elements, TPM, etc) vendors could expose their hardware to web apps in a somewhat generic way. One idea was to have vendor-supplied SW that presented an API via cross-origin message passing. The SW translates API call messages into APDU's that get sent to the hardware and returns the results. I think we were assuming that the main message passing mechanism would be postMessage. It sounds to me like fetch()/navigator.connect() is more network/offline resource oriented and would be a better fit for what we are thinking. --dave _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
