3 ms·
I like https://named-data.net/ https://named-data.net/ approach better, although that requires infrastructure. In short their approach is that instead of conne
by takeda 10y ago
I like https://named-data.net/ https://named-data.net/ approach better, although that requires infrastructure.
In short their approach is that instead of connecting point to point and using addresses of hosts, what if we could address based on the data we want.
This suddenly makes routers aware of what data they are forwarding, that knowledge allows them to start caching and reuse the same data packets when multiple people request the same data.
Things like multicasting or multi path forwarding are simpler. Interestingly, the more people are viewing the same video for example the better, essentially CDN is no longer needed.
Most of use cases how we currently use the Internet, are actually easier to do this way.
Things that are harder though (but not impossible to do) is point to point communication, such as SSH.
- oelmekki 10y agoThis sounds super cool, thanks! (note to others: the description of project can be found here https://named-data.net/project/ https://named-data.net/project/ ) Actually, what could be done without "rebooting" the whole internet is to use caching relays, which would operate just like DNS servers do, but caching content instead of IPs (maybe it's what they're suggesting, it was unclear from general description). EDIT : but I wonder if I'm really ready to deal, as a webdev, with content propagation based on TTL, like we do with dns zones :D EDIT 2 : actually, this is a non issue. TTL is there because when caching something as short as a IP string, you don't want to have to issue a request to parent node. But when caching assets, it won't be that a problem to issue a HEAD http request to asset owner to ask if the cached content should be invalidated.