(hold on for a little bit longer.) I will publish drafts soon of how to using public keys for hosts. All public keys will be stored with a new DNS RR. (I'm writing the drafts at this very moment).
If you are going to comment on this, remember that I sad "hosts".
in a dragrace between fuelcell cars and a tesla model s, the tesla car driver will only see the fuelcell cars in front of him/her. (or is it the other way around? can't seem to remember).
http://www.toecdn.org/ TOECDN will help you to cache all the static content, locally. This should bring your congestion down, depending of course how much of the data is static in the first place.
It's only the ISP who can do this and build such system for caching content.
The concept of TOECDN, The Open Edge Content Delivery Network, previously known as The Last Mile Cache, is to cache content so close to the consumer as possible. TOECDN is the only solution to allow customers to have their own http-cache servers.
Instead of having X different cache solutions for the ISP to host and maintain, TOECDN combines this to ONE unified system/solution for all static content served over HTTP.
And anyone is free to use this solution. That's the hole point.
And you also have this monster thread regarding this (in Swedish) with over 62000 comments! https://www.flashback.org/t1275257 Wikileaks grundare Julian Assange eftersokt for valdtakt i Sverige
Yes it does. Which other cache solutions does allows you as a customer to setup your own cache at home and at the same time is open for anyone to use?
Think of all the websites on the Internet which is run as non-profit. My first thought and example would be wikipedia. They do have alot (alot!) of static content which is the main part of their traffic.
Now add a ISP which is in the third world. Up link via a satellite. How many of the current cache providers would actually place their cache-servers at this ISP? None. To small. On the other hand this is an very good example which will benefit with a cache-server since they do have very limited of bandwidth.
My point is that it will require someone quite big (like wikipedia) to start using TOECDN in the first place. Then the rest will follow.
Have in mind that the concept of TOECDN in released in public domain. Just for the purpose to keep it neutral and for everyone to use.
What I mean is that nobody is interested in TOECDN as a solution to cache static content, independent of whoever is the origin of the content.
With TOECDN you as an ISP only need one setup of cache-servers not one from each content provider (as in my examples). Easier to maintain and to deploy. And its free for everybody to use. Net Neutrality.
Slashdot Mirror
You're blocking the site in the first place so you can not access it.
they are going to release this new feature later this year.
who are you?
No.
(hold on for a little bit longer.) I will publish drafts soon of how to using public keys for hosts. All public keys will be stored with a new DNS RR. (I'm writing the drafts at this very moment).
If you are going to comment on this, remember that I sad "hosts".
in a dragrace between fuelcell cars and a tesla model s, the tesla car driver will only see the fuelcell cars in front of him/her. (or is it the other way around? can't seem to remember).
http://www.toecdn.org/ TOECDN will help you to cache all the static content, locally. This should bring your congestion down, depending of course how much of the data is static in the first place.
The only open solution to solve this bandwidth problem is TOECDN.
http://www.toecdn.org/
where can I watch the hole event and not just some clips?
on the first bitcoin atm and exchange on mars!
TOECDN, The Open Edge Content Delivery Network, will handle this just fine.
No.
You do realize that you should only use TOECDN for static content, right?
It's only the ISP who can do this and build such system for caching content.
The concept of TOECDN, The Open Edge Content Delivery Network, previously known as The Last Mile Cache, is to cache content so close to the consumer as possible. TOECDN is the only solution to allow customers to have their own http-cache servers.
Instead of having X different cache solutions for the ISP to host and maintain, TOECDN combines this to ONE unified system/solution for all static content served over HTTP.
And anyone is free to use this solution. That's the hole point.
http://www.toecdn.org/
no, it will be The Open Edge Content Delivery Network.
http://www.toecdn.org/
http://internationalextraditionblog.files.wordpress.com/2010/12/us-sweden-extradition-supplementary-treaty-35-ust-2501.pdf
The supplementary treaty between Sweden and U.S.
http://blog.foreignpolicy.com/posts/2012/06/25/the_brilliant_legal_calculus_behind_assanges_asylum_request
The legal calculus behind Assange's asylum request
And you also have this monster thread regarding this (in Swedish) with over 62000 comments!
https://www.flashback.org/t1275257
Wikileaks grundare Julian Assange eftersokt for valdtakt i Sverige
No, you are wrong.
We (Sweden) have a separate agreement with the U.S. regarding this. That's why he's scared of being transported to the U.S. from Sweden.
is not Blu-ray quality and thats what we want.
TOECDN trump p2p networks for distribution.
Yeah, don't think so.
(If I mentions TOECDN I'm going to get modded down, so I will not mentions TOECDN).
Yes it does. Which other cache solutions does allows you as a customer to setup your own cache at home and at the same time is open for anyone to use?
Think of all the websites on the Internet which is run as non-profit. My first thought and example would be wikipedia. They do have alot (alot!) of static content which is the main part of their traffic.
Now add a ISP which is in the third world. Up link via a satellite. How many of the current cache providers would actually place their cache-servers at this ISP? None. To small. On the other hand this is an very good example which will benefit with a cache-server since they do have very limited of bandwidth.
My point is that it will require someone quite big (like wikipedia) to start using TOECDN in the first place. Then the rest will follow.
Have in mind that the concept of TOECDN in released in public domain. Just for the purpose to keep it neutral and for everyone to use.
Actually with TOECDN it goes from 14 to 1 solution.
I, as independent content provider can not and are not allowed to use Netflix caching solution. That is not what I call Net Neutrality.
My point with these two examples is that this content is also much cache-able (its static so it doesn't change), so you don't need mirrors anymore!
What I mean is that nobody is interested in TOECDN as a solution to cache static content, independent of whoever is the origin of the content.
With TOECDN you as an ISP only need one setup of cache-servers not one from each content provider (as in my examples). Easier to maintain and to deploy. And its free for everybody to use. Net Neutrality.
It might be exaggerated but you are seeing stories like this one atleast once a week now.
Netflix has its own caching.
Amazon has their own caching.
Akamai has their own caching.
Limewire has their own caching.
Apache has their own caching http://www.apache.org/dyn/closer.cgi/ (talking about download their software, not their cache server).
Sourceforge has their own caching http://sourceforge.net/apps/trac/sourceforge/wiki/Mirrors/.
(I think you can add alot more of my examples).
Why have gazillions of differents caching solutions when you only need one, which honor Net Neutrality by design?