Comments on: Turn Google App Engine into your own Personal Content Delivery Network (CDN)

By: qbantek

qbantek — Thu, 20 Nov 2008 19:20:43 +0000

66.249.91.121 - Fort Lauderdale, FL

By: j1z0

j1z0 — Tue, 07 Oct 2008 10:03:43 +0000

74.125.47.121 from malaysia

By: Robert Gould

Robert Gould — Thu, 02 Oct 2008 15:42:17 +0000

72.14.235.121 from Tokyo

By: Dan

Dan — Mon, 21 Jul 2008 22:06:31 +0000

66.249.81.121 from Scottsdale AZ

By: Don

Don — Wed, 16 Jul 2008 21:51:09 +0000

Years ago I tried CoralCDN for images on a high-traffic website, and it failed really bad. Latency was a big issue, and it’d time out often.

Not sure if this is still an issue, but I’d be happy to read what everyone thinks about CoralCDN.

By: bconzone

bconzone — Mon, 07 Jul 2008 19:23:26 +0000

IP test from 2 computers here in Orlando, FL

1. First machine at work actually routes through our company servers in California so technically CA based machine IP I got is:
72.14.207.121

2. Second which is just off a local Orlando, FL network connection is:
64.233.179.121
119ms

Orlando, FL

By: John Dough

John Dough — Mon, 07 Jul 2008 01:45:46 +0000

66.249.81.121 on the east coast of USA.

By: Nick Berardi

Nick Berardi — Tue, 01 Jul 2008 13:04:48 +0000

Paul,

Honestly everybody is making a big deal about this. All that I was requesting was the option, and it should be pretty easy since Google uses Regex. Honestly standards aren’t worth a hill of beans, if people are referencing the resources in different ways, and you can’t always control the ways people reference your resources in a CDN.

Take for example Yahoo, with their API’s:

http://yui.yahooapis.com/2.4.1/build/menu/assets/skins/sam/menu.css
http://yui.yahooapis.com/2.4.1/build/menu/assets/skins/sam/menu.CSS
http://yui.yahooapis.com/2.4.1/BUILD/menu/assets/skins/sam/menu.CSS
http://yui.yahooapis.com/2.4.1/BUILD/MENU/ASSETS/SKINS/SAM/MENU.CSS

Yahoo tries to follow standards to the “T”, but some standards you just have to ignore because of the human factor, and because they might have made sense at the time but haven’t been updated for the times.

I am not trying to make this an us vs them thing, or a Microsoft vs Apache thing, but the truth is that resources through the URL and the HTTP protocol are better off and easier to use and reference when they are case-insensitive, and isn’t that what the web 2.0 movement is all about.

By: personal content delivery network ... - Irish SEO, Marketing & Webmaster Discussion

Tue, 01 Jul 2008 08:13:41 +0000

[...] content delivery network … Came across this article and found it a pretty interesting read Turn Google App Engine into your own Personal Content Delivery Network (CDN) - Nick Berardi’s … Thought I’d share here. Prices seem quite interesting as well. __________________ Forbairt Media [...]

By: Paul

Paul — Tue, 01 Jul 2008 04:28:35 +0000

Nick,

Apache is only case-insensitive when running on Windows, and that’s only because the underlying filesystem is case-insensitive. Why do you want this behaviour? You might not be interested in what the specifications say, but properly written clients (browsers, caches, accelerators, etc) need to follow them and they’d see your xyz.png URLs as three distinct resources. If you don’t stick to a consistent case convention in all your URLs then you’re slowing your sites down by harming their cacheability.