Re: [w3c/ServiceWorker] Add Request Soft Update algorithm for use by other specifications (PR #1847)

monica-ch left a comment (w3c/ServiceWorker#1847)

Thanks for the review — I reworked this around the `Request Soft Update` wrapper and tightened the user-agent discretion wording in d583ee4.

- The wrapper requires the requesting storage key and returns when it does not match the registration's storage key.
- The user agent may return before running `Soft Update`, allowing it to decline requests to protect against excessive resource use.
- The user agent may coalesce concurrent invocations for the same registration.
- The underlying `Soft Update` algorithm remains unexported.

I used `return` deliberately: WHATWG's algorithm-writing guidance uses it to exit an entire algorithm, whereas “abort these steps” is intended for nested or parallel substeps. This also avoids leaving “throttle” and “ignore” as undefined behavior.

FedCM can use this wrapper with its UA-derived identity-handler storage key; the request remains intentionally best-effort rather than guaranteeing that every invocation starts an update.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/pull/1847#issuecomment-5592875371
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/pull/1847/c5592875371@github.com>