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

@rsolomakhin 

> If we use Cache-Control and the manifest expires, the browser would refetch the manifest without blocking the user.

But if `shop.com` calls:

```js
new PaymentRequest([{
  supportedMethods: ["visa", "bitcoin"]
}, {
  supportedMethods: ['bobpay.com']
}, {
  supportedMethods: ['foopay.com']
}]).show()
```

…and the user has "installed" `bobpay.com` and `foopay.com` as payment apps, but their manaifests are stale, is `show()` now blocked on fetching those manifests? If one of those requests hangs, is the whole UI hanging?

> Can Service Workers give more control to the developers as to when their manifests should be updated?

It's something that could be added in future, but not right now. However, service worker already gives the developer full control over when service worker registrations and other forms of storage are updated.

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