Friday, July 04
We Interrupt This Rant
SofLayer have fixed their content delivery network.
I signed up (and have been paying for) this service the moment it was announced, because (a) it's cheap and (b) they have a very good distribution of nodes across North America, Europe, the nicer parts of Asia (Tokyo, Singapore and Hong Kong), and Australia.
Except their DNS was hosed, and I variously got routed to Atlanta, New York, Los Angeles, Toronto, or Tokyo, depending on the time of day and the humidity.
This made a potentially great product about 98% useless.
But now, they've fixed it. When I look for the local node, I get the local node. Which is right here in Sydney. 14ms away.
I have accounts for it for both mu.nu and mee.nu. I'll be integrating it into the system over the next couple of months. What it will mean is that without changing anything from the user's point of view, all your files will be automatically backed up all over the world (free 20-way redundancy!) and will show up much faster for people who don't already live in Texas.
Your file URLs may change, though. Instead of myblog.mee.nu/images/boobies.jpg, it will get translationed into something like cdn.mee.nu/meenu/myblog/images/boobies.jpg. The old URL will still work, but won't be able to take advantage of the CDN.
Comments are disabled.
Post is locked.
SofLayer have fixed their content delivery network.
I signed up (and have been paying for) this service the moment it was announced, because (a) it's cheap and (b) they have a very good distribution of nodes across North America, Europe, the nicer parts of Asia (Tokyo, Singapore and Hong Kong), and Australia.
Except their DNS was hosed, and I variously got routed to Atlanta, New York, Los Angeles, Toronto, or Tokyo, depending on the time of day and the humidity.
This made a potentially great product about 98% useless.
But now, they've fixed it. When I look for the local node, I get the local node. Which is right here in Sydney. 14ms away.
I have accounts for it for both mu.nu and mee.nu. I'll be integrating it into the system over the next couple of months. What it will mean is that without changing anything from the user's point of view, all your files will be automatically backed up all over the world (free 20-way redundancy!) and will show up much faster for people who don't already live in Texas.
Your file URLs may change, though. Instead of myblog.mee.nu/images/boobies.jpg, it will get translationed into something like cdn.mee.nu/meenu/myblog/images/boobies.jpg. The old URL will still work, but won't be able to take advantage of the CDN.
Posted by: Pixy Misa at
12:34 PM
| Comments (3)
| Add Comment
| Trackbacks (Suck)
Post contains 218 words, total size 1 kb.
1
If I do a file upload, will the upload page give me the new CDN version of the URL for that file? (Once you've finished integrating it, of course)
Posted by: Steven Den Beste at Friday, July 04 2008 12:59 PM (+rSRq)
2
Good thinking. Yep, I'll do that.
I'm also going to make the BBCode tags automatically handle the conversion where possible, but for people not using BBCode, it certainly makes sense to display the CDNified URL.
I'm also going to make the BBCode tags automatically handle the conversion where possible, but for people not using BBCode, it certainly makes sense to display the CDNified URL.
Posted by: Pixy Misa at Friday, July 04 2008 01:03 PM (PiXy!)
3
I think we'll need a man page when the time comes. And will it apply to existing images, or only newly-loaded ones?
Oh, and BTW, the upgraded javascript comment formatter now works in k-meleon. Win!
Oh, and BTW, the upgraded javascript comment formatter now works in k-meleon. Win!
Posted by: Old Grouch at Friday, July 11 2008 08:22 AM (VUYEY)
41kb generated in CPU 0.0129, elapsed 0.1228 seconds.
56 queries taking 0.1138 seconds, 232 records returned.
Powered by Minx 1.1.6c-pink.
56 queries taking 0.1138 seconds, 232 records returned.
Powered by Minx 1.1.6c-pink.
