Re: [ServiceWorker] Soft Update and Register can race when setting registration scriptURL (#789)

I understood the problem pointed by @wanderview. Mutating the registration's registering script url from the concurrently running main threads (Register, update(), Soft Update) shouldn't be allowed.

Marking a url for an Update from @matto's comment seems to be able to be specified as passing an argument to Update algorithm as @wanderview suggested as that's the place where the job is scheduled.

I think we still have to decide between 1) Blink's behavior: **schedule and abort when newest worker's url was changed** and 2) Gecko's suggestion: **use newest worker's url when job begins** for update jobs. @wanderview will it be okay to conform to what Blink already implemented for this? If so, the Update algorithm can take a script url as a (non-optional) argument and check if the given url is not the same as the newest worker's script url before continuing with further steps.

I'll address the decision once I'm back to work.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/789#issuecomment-159173787