3 ms·
Does it also affect caching via service workers? Pretty standard practice in PWAs.
by iaml 8y ago
Does it also affect caching via service workers? Pretty standard practice in PWAs.
- pjmlp 8y agoNo, but it impacts the initial download as it needs to be end to end, instead of the closest access point. Also a very good way to waste traffic quota, e.g. a school network connection vs students computers.
- pythonaut_16 8y agoWhich interestingly is a problem IPFS would solve, right? But IPFS potentially introduces other drawbacks. It would be cool to able to build dual-distribution applications, where publicly available assets and content blobs (e.g. app.js) could be distributed in an immutable, cache-able manner, and server interactions and private assets could still be handled in a more traditional client/server way. Perhaps then we might even be able to realize the original intent of including dependencies from a CDN, being able to share a cached version of React across websites. (I'm not and IPFS advocate or detractor)
- judah 8y agoNo, HTTP caching and PWA web worker caching works fine. (In fact, web workers require HTTPS to even function.) Eric Meyer's "HTTPS busts caching" complaint refers not to HTTP or web worker caching, but man-in-the-middle local servers caching responses. It sits between the internet and your local box, and serves cached requests. This breaks with HTTPS, which is designed to break man-in-the-middle attacks.