undefined | Better HN

0 pointszac23or8mo ago0 comments

>cache.delete obviously only deletes that browser's cache, not all other browsers in the world.

To me, it only makes sense if the put method creates a cache only in the datacenter where the Worker was invoked. Put and delete need to be related, in my opinion.

Now I'm curious: what's the point of clearing the cache contents in the datacenter where the Worker was invoked? I can't think of any use for this method.

My criticisms aren't about functionality per see or developers. I don't doubt the developers' competence, but I feel like there's something wrong with the company culture.

0 comments

kentonv8mo ago

> To me, it only makes sense if the put method creates a cache only in the datacenter where the Worker was invoked. Put and delete need to be related, in my opinion.

That is, in fact, how it works. cache.put() only writes to the local datacenter's cache. If delete() were global, it would be inconsistent with put().

> Now I'm curious: what's the point of clearing the cache contents in the datacenter where the Worker was invoked? I can't think of any use for this method.

Say you read the cache entry but you find, based on its content, that it is no longer valid. You would then want to delete it, to save the cost of reading it again later.

zac23orOP8mo ago

> cache.put() only writes the local datacenter's cache.

Thanks, I didn't know that (I don't remember reading it in the documentation)

j / k navigate · click thread line to collapse