9 ms·
That's so cool! I actually made a YouTube video on why I don't use CF anymore. Shameless plug here :D https://youtu.be/TWtGwW_e56w https://youtu.be/TWtGwW_e56w
by martinbaun 2y ago
That's so cool! I actually made a YouTube video on why I don't use CF anymore. Shameless plug here :D
https://youtu.be/TWtGwW_e56w https://youtu.be/TWtGwW_e56w
I really love your idea of doing content hash for (permanent?) cache. I'll definitely do that. Right now we use a semi-permanent cache, but sometimes we screw up and it really bites us. If it is hashed you know for sure it is permanent. It reminds of IPFS, but for your little corner of the internet :D
- stephenr 2y agoWe started using content hash addressing with our assets build system (i.e. combining CSS & JS into a single URL), so that we'd get maximum cache life without needing to artificially manage cache busting query strings. The more substantial use now though, is for the "content" of the site (purchasable ebooks/etc and associated artwork) which is constantly growing and occasionally old content gets updated with newer editions/revisions. We use content hashing to actually store the files (free de-duplication) and obviously it then gives us the same caching benefits.
- martinbaun 2y agoThis is so cool Stephen. I'd love to hear more. This is definitely something I could use in one of my clients projects. You wanna schedule maybe a meeting next week? https://martinbaun.com/book/ https://martinbaun.com/book/
- stephenr 2y agoI'd be happy to talk about it more, but I'll be out of the office all next week on a short break. Can you drop me an email (it's in my profile) with a rough idea of what you want to discuss, and we could follow up the following week ( with a call/chat?
- martinbaun 2y agoAwesome Steven, I'll msg you once you're back. Happy break