W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)

From: adamroach <notifications@github.com>
Date: Thu, 19 May 2016 06:47:06 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc:
Message-ID: <w3c/webpayments/issues/130/220328938@github.com>
@tommythorsen wrote:
>  Will these payment apps then ignore the POST'ed payment request and use `navigator.payments.getRequest()` instead? I feel that this is very inelegant, and that there isn't that much benefit to be had from doing it this way.

No, they would call `ServiceWorkerContainer.register()`, which would cause the local payment app to be activated whenever an appropriately-scoped POST is called. The local payment app would then handle this POST response in the same way as a remote payment app does.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/130#issuecomment-220328938
Received on Thursday, 19 May 2016 13:48:07 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 May 2016 13:48:07 UTC