Based on the conversation with @adamroach in #104, I've made another document that explores how to match Payment Apps and Service Workers, [here](https://github.com/tommythorsen/webpayments-demo/blob/gh-pages/proposals/Apps%20and%20Workers%202.md). This time, we do not depend on a Web App Manifest. This lets us get around the problem of defining what the Payment App is. The only downside to doing this, is that we don't have any kind of identifier for the Payment App any more, but this is only a problem if we want to merge Options and Wallets from different Service Workers within the same App. As I mention in the document, we could get around this by specifying a "Payment App Id" from the Service Worker. This would let us consider all Service Workers with the same Payment App Id as belonging to the same Payment App. -- 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/105#issuecomment-282985135
Received on Tuesday, 28 February 2017 09:16:58 UTC