Re: [ServiceWorker] Is fetchEvent.client a performance concern? (#723)

aah, cool!

@jungkees Sorry for the delay.  So my use case is having shared state in the service worker, but I want each client to have a unique descriptor that isn't tied to the service-worker-internal name of the resource.  Sort of like a file descriptor, actually, and like FDs it would be nice to use something like small integers rather than something like long uncollidable cryptographic hashes.  What I need from the browser is an unforgable `clientId`, I don't need any of the other info I can imagine being populated by `getClient`.  And additionally because I want to get this `clientId` on almost every request, its a bit nicer that it is sync than async.  So, it sounds like I'm late to the party, but its neat to hear this is in v1.

@jakearchibald are these races in the spec or implementation?  I'd be interested in lending some eyes.

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