Also, how much latency does this add due to P2P connection set up time?
CacheP2P – Distributed caching platform
21–30 of 63 posts
Re: CacheP2P – Distributed caching platform
#22Sounds cool, but what are the use-cases? What problems is this tech trying to solve?
Well, should all DNS servers suddenly die it might be useful but besides that..
But, yeah, still kind of cool.
Re: CacheP2P – Distributed caching platform
#23Re: CacheP2P – Distributed caching platform
#24Im not saying its realistic to engineer sha1 collisions to serve up malicious content on a platform like this, but its getting closer every year.
Re: CacheP2P – Distributed caching platform
#25Sounds cool, but what are the use-cases? What problems is this tech trying to solve?
I have the same issue - can't think of a single one. Most of the ones I could think of are solved better with CDN or other cloud services. Well, should all DNS servers suddenly die it might be useful but besides that.. But, yeah, still kind of cool.
This scales asset availability with popularity, automatically, for free, with minimal setup.
Re: CacheP2P – Distributed caching platform
#26Re: CacheP2P – Distributed caching platform
#27So you have to load the page from the server in order to load the javascript so you can load the same page from the client pool? Is this supposed to be more of a bootstrap process? Load the first page from the server and then you can use the URL hash to request additional pages from the connected clients?
Re: CacheP2P – Distributed caching platform
#28Re: CacheP2P – Distributed caching platform
#29Re: CacheP2P – Distributed caching platform
#30I'm getting this error on your API page: cachep2p.min.js:9 Uncaught Error: Cannot add duplicate torrent 3cd9bdf4916f422aa77cdd1b952c14202e0eafca I'm also getting these on FF: ICE failed, see about:webrtc for more details(unknown) TypeError: asm.js type error: expecting argument type declaration for 'e' of the form 'arg = arg|0' or 'arg = +arg' or 'arg = fround(arg)'