CDN - Revision history

Tom: /* Context */

2023-04-27T17:42:17Z

‎Context

Tom: /* Other Material */

2022-09-04T21:36:26Z

‎Other Material

Tom: /* Full Title or Meme */

2020-11-08T00:23:05Z

‎Full Title or Meme

Tom: /* Full Title or Meme */

2020-11-08T00:22:48Z

‎Full Title or Meme

Tom: /* Context */

2020-11-07T20:37:19Z

‎Context

Tom: /* References */

2020-11-07T20:35:34Z

‎References

Tom: /* Context */

2020-11-07T20:34:38Z

‎Context

Tom: /* Context */

2020-11-07T20:29:02Z

‎Context

Tom: /* Context */

2020-11-07T20:25:36Z

‎Context

Tom at 20:22, 7 November 2020

2020-11-07T20:22:53Z

@@ Line 7: / Line 7: @@
 ==Context==
 The CDN can be just deliver traditionally addressed content, like URL's very quickly, or it can be a full distributed [[Content Addressable Storage]]
-* In the centralized world using a CDN to serve your commonly used javascript and css files (say like jQuery or Bootstrap) is advised for a variety of reasons. Most of them still hold true, but only if applied to a centralized world.<ref>markg85 ''How to properly use the link href in websites for ideal IPFS and browser usage?'' https://discuss.ipfs.io/t/how-to-properly-use-the-link-href-in-websites-for-ideal-ipfs-and-browser-usage/9387</ref>
+* In the centralized world using a CDN to serve your commonly used javascript and css files (say like jQuery or Bootstrap) is advised for a variety of reasons. Most of them still hold true, but only if applied to a centralized world.<ref>markg85 ''How to properly use the link href in [[Web Site]]s for ideal IPFS and browser usage?'' https://discuss.ipfs.io/t/how-to-properly-use-the-link-href-in-websites-for-ideal-ipfs-and-browser-usage/9387</ref>
-* Using a CDN in a decentralized world all of a sudden gives your super awesome cool shiny website a single point of failure! I personally found this out a couple times now when once of my IPFS play sites was acting suspiciously slow. I am using Bootstrap and the CDN to serve it was acting really slowly (in this case it was this file on bootstrapcdn).
+* Using a CDN in a decentralized world all of a sudden gives your super awesome cool shiny [[Web Site]] a single point of failure! I personally found this out a couple times now when once of my IPFS play sites was acting suspiciously slow. I am using Bootstrap and the CDN to serve it was acting really slowly (in this case it was this file on bootstrapcdn).
 * So, why use a CDN at all? Sure, in the old paradigm of centralized sites the before mentioned reasons in favor of it still hold. But in a distributed world this can be painful.
 * To change sites to be content that is served from IPFS. But  how to even do this in such a way that it’s most efficient for IPFS and the browser?

← Older revision		Revision as of 21:36, 4 September 2022
Line 46:		Line 46:

	[[Category: Glossary]]		[[Category: Glossary]]
		+	[[Category: Networking]]

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-The Content Delivery Network ([[CDN]]) is designed to deliver static data to web data consumer's quickly regardless of location or network load.
+The Content Delivery Network ([[CDN]]) is designed to deliver static data to web data consumers quickly regardless of location or network load.
 ===Alternative Meanings===

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-The Content Delivery Network ([[CDN]]) is designed to deliver static data to web sites quickly regardless of location or network load.
+The Content Delivery Network ([[CDN]]) is designed to deliver static data to web data consumer's quickly regardless of location or network load.
 ===Alternative Meanings===

@@ Line 7: / Line 7: @@
 ==Context==
 The CDN can be just deliver traditionally addressed content, like URL's very quickly, or it can be a full distributed [[Content Addressable Storage]]
-* In the centralized world using a CDN to serve your commonly used javascript and css files (say like jQuery or Bootstrap) is advised for a variety of reasons. Most of them still hold true, but only if applied to a centralized world.<ref>markg85 ''https://discuss.ipfs.io/t/how-to-properly-use-the-link-href-in-websites-for-ideal-ipfs-and-browser-usage/9387'' https://discuss.ipfs.io/t/how-to-properly-use-the-link-href-in-websites-for-ideal-ipfs-and-browser-usage/9387</ref>
+* In the centralized world using a CDN to serve your commonly used javascript and css files (say like jQuery or Bootstrap) is advised for a variety of reasons. Most of them still hold true, but only if applied to a centralized world.<ref>markg85 ''How to properly use the link href in websites for ideal IPFS and browser usage?'' https://discuss.ipfs.io/t/how-to-properly-use-the-link-href-in-websites-for-ideal-ipfs-and-browser-usage/9387</ref>
 * Using a CDN in a decentralized world all of a sudden gives your super awesome cool shiny website a single point of failure! I personally found this out a couple times now when once of my IPFS play sites was acting suspiciously slow. I am using Bootstrap and the CDN to serve it was acting really slowly (in this case it was this file on bootstrapcdn).
 * So, why use a CDN at all? Sure, in the old paradigm of centralized sites the before mentioned reasons in favor of it still hold. But in a distributed world this can be painful.

@@ Line 40: / Line 40: @@
 ==References==
 * [https://www.cloudflare.com/learning/cdn/what-is-a-cdn/ What is a CDN?] from Cloudflare.
 [[Category: Glossary]]

@@ Line 9: / Line 9: @@
 * In the centralized world using a CDN to serve your commonly used javascript and css files (say like jQuery or Bootstrap) is advised for a variety of reasons. Most of them still hold true, but only if applied to a centralized world.
 * Using a CDN in a decentralized world all of a sudden gives your super awesome cool shiny website a single point of failure! I personally found this out a couple times now when once of my IPFS play sites was acting suspiciously slow. I am using Bootstrap and the CDN to serve it was acting really slowly (in this case it was this file on bootstrapcdn).
+* So, why use a CDN at all? Sure, in the old paradigm of centralized sites the before mentioned reasons in favor of it still hold. But in a distributed world this can be painful.
-This made me think, why would i use a CDN at all? Sure, in the old paradigm of centralized sites the before mentioned reasons in favor of it still hold. But in a distributed world this can be painful.
+* To change sites to be content that is served from IPFS. But  how to even do this in such a way that it’s most efficient for IPFS and the browser?
+* Lets take just the css bootstrap as an example. Before i changed anything (thus when using the CDN) i had:
   <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css" integrity="sha384-ggOyR0iXCbMQv3Xipma34MD+dH/1fQ784/j6cY/iJTQUOhcWr7x9JvoRxT2MZw1T" crossorigin="anonymous">
-Now i can use a relative path (and drop the rest) which makes it look like:
+Now we can use a relative path (and drop the rest) which makes it look like:
    <link rel="stylesheet" href="bootstrap.min.css">
-Or i can use a specific IPFS path (only works if ipfs is in the protocol list and set with companion)
+Or we can use a specific IPFS path (only works if ipfs is in the protocol list and set with companion)
   <link rel="stylesheet" href="ipfs://QmNrgEMcUygbKzZeZgYFosdd27VE9KnWbyUD73bKZJ3bGi">
@@ Line 30: / Line 27: @@
 Another alternative is to use a gateway (at the cost of adding a single point of failure again):
-<link rel="stylesheet" href="https://ipfs.sc2.nl/ipfs/QmNrgEMcUygbKzZeZgYFosdd27VE9KnWbyUD73bKZJ3bGi">
+ <link rel="stylesheet" href="https://ipfs.sc2.nl/ipfs/QmNrgEMcUygbKzZeZgYFosdd27VE9KnWbyUD73bKZJ3bGi">
 What am i supposed to provide in the href section to make full use of IPFS? By that i mean that the browser requests the data from IPFS and uses that as cache. I’m asking because the browser (chrome in this case) and based on this information likely has no clue that the file came from IPFS. Therefore it likely doesn’t know that bootstrap.min.css is shared over multiple sites and thus downloads it for every site.