Skip to content
This repository has been archived by the owner. It is now read-only.

Is content-addressing faster than location-addressing? #150

Closed
RichardLitt opened this issue Jul 28, 2016 · 2 comments
Closed

Is content-addressing faster than location-addressing? #150

RichardLitt opened this issue Jul 28, 2016 · 2 comments

Comments

@RichardLitt
Copy link
Contributor

RichardLitt commented Jul 28, 2016

Another way this could be phrased, I think, is this: Is searching through a merkledag data structure faster than a traditional filesystem? Or: How is IPFS faster than HTTP (and does that question make sense?)?

@warlord500
Copy link

warlord500 commented Dec 1, 2016

content addressing and location addressing just ways to refer to a particular file. neither is necessarily slower or faster. location addressing tells the computer where to find a file. content addressing says uses this file/data with this hash for this purpose. content doesn't tell you how to get said file. while location addressing does.

with content addressing I can technically get the file from more places because as long as the file matches the hash I referring to the same data. so I could techinally get the file from my neighbor.
as long as check the hash,

however location addressing usually refers to a single location on the internet. It means to get said file I have to trust that server.

@flyingzumwalt
Copy link
Contributor

flyingzumwalt commented May 23, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants