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

If we use Cache-Control and the manifest expires, the browser would refetch
the manifest without blocking the user. If the manifest fails to download
due to network troubles, e.g., timeout, then browser should not uninstall
the associated apps.

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

On Sep 11, 2016 7:13 AM, "Jake Archibald" <notifications@github.com> wrote:

> I was thinking of using Cache-Control for manifest expiration.
>
> So if the manifest expires, is it no longer an installed payment app? Or
> will every matching stale manifest be refetched when a site calls new
> PaymentMethodData()? What if one of those requests hangs?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webpayments-payment-apps-api/issues/33#issuecomment-246182340>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA-yGdhF5rCowQ2MepbBlaHYCQuaobFMks5qpAyEgaJpZM4Jt-H8>
> .
>


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