- From: Jake Archibald <notifications@github.com>
- Date: Wed, 14 Sep 2016 07:26:15 -0700
- To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
Received on Wednesday, 14 September 2016 14:26:56 UTC
> Now, an argument could be made that Payment Apps that provide multiple APIs could, for example, in their service worker do a fetch to obtain their manifest, parse it, and then provide it as JavaScript to the paymentAppManager interface This sounds like the most extensible thing to do. This means the developer could have the data directly in the service worker, or an external JSON resource, or YAML, or whatever they want. -- 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-payment-apps-api/issues/33#issuecomment-247030424
Received on Wednesday, 14 September 2016 14:26:56 UTC