| |||||||||||||
Content-centric networking with CCNxContent-centric networking with CCNxPosted Oct 25, 2012 14:13 UTC (Thu) by n8willis (editor, #43041)In reply to: Content-centric networking with CCNx by rswarbrick Parent article: Content-centric networking with CCNx
Caching is predicated on the notion that there is one canonical version of the file, and the various cached versions are copies. In CCN, all versions of the file are equivalent (assuming the SHA-256 hash validates, that is). In HTTP, an end node could always request the original directly from the server if it doesn't trust the cache, but in CCN that gains you nothing since you can verify the correctness of the data yourself with the signature; consequently there is no mechanism to do so. Perhaps more importantly, intermediate nodes do not need to perform age calculations or any of the other cache-control mechanics.
Nate
(Log in to post comments)
Content-centric networking with CCNx Posted Oct 25, 2012 14:46 UTC (Thu) by rswarbrick (subscriber, #47560) [Link]
Ah, I think I understand you. So the equivalent with an HTTP cache would require that (a) The contents at a given URL never changed and (b) The URL somehow also gave a hash of the contents so that you could check you'd got the right thing.
Yep, I agree that this is different from a caching proxy :-)
|
|||||||||||||