- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Thu, 7 Jul 2016 17:09:01 +0200
- To: Adam Roach <abr@mozilla.com>, "Michael[tm] Smith" <mike@w3.org>
- Cc: Web Payments Working Group <public-payments-wg@w3.org>, Florian Rivoal <florian@rivoal.net>
Other advantages of Native Messaging (using any of the current proposals) compared to using HTTP include: - Potentially eliminating session state-holding outside of what is usually already provided through the invoking Web page. - Enables (voluntarily) reuse of the the browser's communication facilities (like "fetch()") which means that external communication required by invoked Apps would be subject to the same security constraints (SOP, CORS, etc) as "real" Web applications, whereas Apps POSTing data OOB are free breaking such rules whenever they want. - Better alignment with Wallets using NFC/BLE since these typically do not require Internet connectivity; they rather need a bi-directorial "channel" to the merchant. The exact nature of this channel can easily be abstracted. anders
Received on Thursday, 7 July 2016 15:09:42 UTC