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

I'm not too worried about this. In fact, it seems worse that users would have to manage the lifecycle of yet another thing.

If it's a JS context that wakes up to handle an event, potentially without a page on the origin being open, that's a service worker. This is why things like push, sync, and potentially alarms & geofencing live there. The precedent is already there, and [by design](https://w3c.github.io/ServiceWorker/spec/service_worker/index.html#extensibility).

Joining these menas developers could use push messages to update a payment app's details etc.

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