Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33)

It sounds to me like option 2 is the best option until option 3 clearly becomes a necessity. Polluting the `ServiceWorkerGlobalScope` with payment-specific stuff will not only be ugly, but it will set a bad precedent. Furthermore, there is, in my view, a great advantage to developers in "saying what you mean" with appropriately named payment app registration methods and messages and so forth.

Having to interpret something based on the context because it happens to "look like" what you want requires that you take on considerably more (unnecessary) knowledge about the underlying architecture and details of the system that has been extended. Let's keep this as simple as we can
for developers and not introduce any mysteries that they may feel they need to go off and solve to really understand the API.

-- 
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-242766255