Akamai Wins Lawsuit to Protect Obvious Patent 173
brandaman writes "Akamai, the largest content delivery network (CDN) with about 70% market share, recently won its lawsuit against the against second largest CDN - Limelight Networks. The suit asserted that Limelight was infringing on Akamai's patent which, upon examination, seems to be somewhat on the obvious side. 'In accordance with the invention, however, a base HTML document portion of a Web page is served from the Content Provider's site while one or more embedded objects for the page are served from the hosting servers, preferably, those hosting servers near the client machine. By serving the base HTML document from the Content Provider's site, the Content Provider maintains control over the content.' Limelight is obviously not pleased, and this is not the first lawsuit Akamai has won regarding its patents."
I'm in trouble now. (Score:5, Funny)
Google has used Akamai's network (Score:2, Informative)
Akamai Made Microsoft Run on Linux (Score:5, Informative)
Re:I'm in trouble now. (Score:5, Informative)
The way Akamai works is it distributes the "heavy duty" content like images, scripts. to its own servers all around the world. It then lets its customers (like E*Trade, to pick one actual example) modify their static HTML content to refer to those images in a special way. For example, the E*Trade home page has the following link in it for one of its images:
https://a248.e.akamai.net/n/248/1777/20080228.0/www.etrade.com/images/prospect/topGrad.gif [akamai.net]
The url is specially encoded in such a way that when your local DNS server queries a248.e.akamai.net, the DNS server returns a server located physically near you. So if you're in England a248.e.akamai.net might resolve to an IP located in Londan, but in New York City it would resolve to an IP somewhere in New York. Then when the http request is sent, Akamais servers decode that annoyingly long URL to determine which customer of theirs it is and serve up the correct image. It's actually a fairly complex and fast process. If the server that you're directed to doesn't actually have the image locally then that Akamai server will query another nearby Akamai server. If that server also doesn't have it then it'll actually pull the image down from a master server that E*Trade uploaded the image to.
You can test this out yourself by looking up the IP address of a248.e.akamai.net yourself. Locally you'll get one IP. If you do a google search for dns lookup tools you can submit that domain name to other sites to look it up and you'll get totally different IP's that are physically close to wherever that domain lookup tool runs from.
The bottom line is that it's a prety complex process that involves both the use of DNS to ensure you download large chunks of content from physically near servers as well as some pretty sophisticated caching in the background to make sure static content is delivered rapidly no matter where in the world you are.
I used to work at Akamai so I have a pretty good firsthand knowledge of how their stuff works. I doubt a lot of their algorithms they use would pass the "obviousness" test...
Re:I'm in trouble now. (Score:5, Insightful)
I am not familiar with this particular case, but the big issue here is that Akamai might be trying to patent the general concept of distributing cache servers around the world. This is the kind of thing that the patent office should not allow. If I have a better way to do this, or even the same way, I should be allowed to do it. Akamai is the leader in this industry and they are well set and nobody is going to knock them off the map suddenly one day by copying them. They don't need patent protection. Furthermore, this is the kind of thing any group of competent developers can create, and 10 different groups would have 10 different ways of doing it. Even if a patent is appropriate here, it should not be used to squash similar competing services.
Re: (Score:3, Informative)
They are now under the "business process" umbrella. The courts are accepting these so far.
Re:I'm in trouble now. (Score:5, Interesting)
Yeah, lower US courts decided to start allowing software patents.
However in the current Microsoft-AT&T case before the US Supreme Court the multiple justices were clearly skeptical of that behavior. In particular:
JUSTICE BREYER: I take it that we are operating under the assumption that software is patentable? We have never held that in this Court, have we?
MR. JOSEFFER [DOJ Atty]: No, but as I was saying before -
JUSTICE BREYER: So what should we do here? Should, if we are writing this, since it's never been held that it's patentable in this Court
I have read the Supreme Court rulings relating to software patents. The rulings were back in the early 80's or so, back before the lower courts went off on their software patent kick. It seems clear to me that the lower courts have ignored or directly violated several points of Supreme Court law in those rulings. It appears that the Supreme Court is looking to directly rule on the subject and reign in the aberrant lower courts.
-
Re: (Score:2)
Chemistry and genes didn't used to be patentable, but they ended up that way anyhow after long arguments.
Re:I'm in trouble now. (Score:4, Informative)
I've spent plenty of time, as I said in my post I've actually read all of the Ssupreme Court rulings on the subject.
A number is not an "invention". An equation is not an "invention". A calculation is not an "invention". Mental information processing is not an invention. Mental information processing does not magically become a patentable invention when you OBVIOUSLY use a calculator to accelerate/automate it. Mental information processing does not magically become a patentable invention when you OBVIOUSLY use a computer to accelerate/automate it. Mental information processing does not magically become a patentable invention when you OBVIOUSLY do it on the internet to accelerate/automate it.
The Supreme Court has explicitly ruled that no possible algorithm can ever qualify as "novel" or "non-obvious" for patent purposes. Therefore no possible software can ever qualify as novel, no possible software can ever qualify as non-obvious, no possible software can ever be an invention. There is nothing novel or non-obvious in blatantly using an ordinary computer to carry out that "non-novel" "obvious" calculation. Sticking the words "on a computer" at the end of a mathematical information manipulation does not magically turn it into a patentable invention.
It doesn't matter if you are the first person to write down some particular number, it cannot be "novel". It doesn't matter how many digits long your number is, it cannot be "non-obvious". No possible math, no possible information processing, no possible mental process, no possible algorithm, no possible software, can ever be an invention. As the Supreme Court said, they can never qualify as novel or non-obvious for the same reason that laws of physics are never treated as novel or non-obvious for patent purposes. An invention may make use of gravity, but G=M1*M2/R^2 is not an invention and it is treated as non-novel and as obvious, even if you are the first person to figure it out.
Chemistry and software are not really that different philosophically
No matter how long I *think* about a chemical reaction I will never actually make any molecules.
Physical objects and physical processes are philosophically different than math/calculations/mental-processes.
Physical objects and physical processes are concretely different than math/calculations/mental-processes.
-
Re: (Score:3, Informative)
Okay, so then you can enlighten me, the half-knowing. To my knowledge the whole mess started with the Supreme Court rebuking the USPTO in the Diamond vs. Diehr case, where the USPTO was kind of ordered to grant a patent on essentially software. Yes, I read the patent and some resources around it. Yes, the Supreme Court held the earlier appeals for non-patentable. Though in Diamond vs. Diehr th
Algorithms not patentable? (Score:3, Insightful)
What about RSA, LZW, LZS and MP3?
Re: (Score:2)
In your case, implementing particular equations for the purpose of compression and encryption would definitely be patentable IF (that's a big IF) they also meet the other criteria for patentability.
Re: (Score:2)
Great. I wonder if the fact that DNS was specifically designed with this sort of thing in mind undermines Akamai's inventiveness here?
Of course it's pretty pointless speculating here, since TFA has exactly zero information about what's specifically being infringed here: could be something of substance, or could be the old "use a more or less complex
Re: (Score:2)
Was doing this in 1998 - offshore gambling (Score:2)
The site was called "Wager Web", but I don't think it exists anymore. After the off-shore clients st
It may be obvious but (Score:4, Insightful)
As I am not a lawyer, it was not obvious to me what they were patenting.
Is this patenting having the html on one server and the rest (pictures etc) on other ones?
If it is that, I think there should be some prior art in the original stuff from Tim Berners-Lee.
Re: (Score:3, Informative)
Apparently only in the specific case of having the "other ones" be distributed across the network and with the "closest" server to the client chosen to download the content from.
I suppose that things like mirrors, etc. don't count because in that case the user typically chooses what they believe to be the closest server rather than the host or akamai.
Re: (Score:2)
Apparently only in the specific case of having the "other ones" be distributed across the network and with the "closest" server to the client chosen to download the content from.
Without having read the patent (mea culpa) your description sounds damning in terms of obviousness and probability of prior art.
I have two issues with Akamai now: first, sitting front and centre in the evil patents problem, playing a starring role as a patent troll. Second, being a Linux freeloader. A grep of my lkml mailbox reveals zero Akamai email addresses. Not at all becoming a multibillion dollar business that built itself largely on the back of low cost Linux servers.
Genuity in 1997, "Hopscotch" protocol (Score:5, Informative)
I found this article ( http://findarticles.com/p/articles/mi_m0EIN/is_1997_Dec_10/ai_20053332 [findarticles.com] ) rather easily, going back to 1997.
Re: (Score:2)
I can't find it, but somebody patented storage in the door of a refrigerator. That seems obvious, but a true improvement. They had 17 years to exploit the monopoly on refrigerators with door storage.
My wife worked at a paper company. They had patents on how to cut cardboard to make containers (french fry boxes, etc)
Obvious stuff can be patented.
Re:It may be obvious but (Score:5, Insightful)
People pereenially confuse the theory of the patent system (reward the poor starving inventors) with its actual empirical effects (allowing corporatist elites to control innovation and the very direction of a technological society).
Re: (Score:3, Interesting)
Re: (Score:3, Interesting)
Only parts are very obvious (Score:5, Informative)
As in many of these "obvious patent" trolling articles, the article/summary oversimplify the patent. The patent does not just claim click here, fetch there redirection which is used by just about every major site, but algorithms for doing the load balancing etc.
If you read some of the claims, then you'll see that various algorithms are used for load balancing and other purposes. While these might be obvious to some, they are extremely obvious to all.
The test of "obvious" is also not that clear cut. IIRC, the tests is "reasonably obvious to practitioners of the art". This test should be applied to the state of the art as at the time of the patent, because a patent "teaches" the industry and therefore after the disclosure the less-than-obvious become obvious.
Six Years Of So Obvious, No One Thought Of It (Score:2)
They didn't file the patent until '99.
If it's that obvious, one would assume there's prior art from that six year window.
If it had been filed in say '95 when there wasn't that much interest in the web yet, that'd be one thing. By '99, a hell of a lot of people were using it and filing IPOs as fast as they could come up with ideas.
The alternative explanation would be that it wasn't all that obvious and the obviousness either comes from retrospect
So Obvious, people were already doing it (Score:5, Insightful)
We also had a Internet gambling site at the time which used at least elements of the patent in that it was an off-shore (for legal reasons) site with static content served domestically for performance through multiple NAP connections with some routing magic. No where near as advanced as either Genuity or the design we were working on, but obviously pointing toward that goal.
A guy, possibly by the name of Alex Yuriev, was talking about distributed sites and dynamic routing in Philadelphia in 1996-1997. He may have worked for NetAccess at that point and was a bit genius with BGP and routing in general. My business partner at the time talked back and forth with him about some of the similar things we were working on.
The base concept is just not that hard, and the most difficult part of the implementation is physical and logistical, not technical. The hard technical part is doing dynamic updates to the distributed systems and synchronizing transactions, but even that can be fudged decently if you are willing to go with the 90% solution that gives you most of the benefit.
So basically, there was a lot of activity on this sort of thing in the 90's, the technology was clearly driving in that direction, and it becomes easy once the underlying tools are in place.
They are talking about Edge Side Includes (Score:3, Interesting)
ESI is like Server Side Includes, except that the included part resides on the Edge servers. So your server would serve a page with only the content personalized to you specifically (like the fact that you are logged in) but a box full of news headlines that everyone sees would be included by the edge server.
Not entirely obvious, but I am not so sure it warrants patent protection in any case.
Re: (Score:2)
Re: (Score:2)
But read the link I pointed to about ESI. Akamai does more than just server dependencies like images, video, css, js, etc. They actually have an engine that assembles HTML also.
That said, I don't think any more this is specifically about ESI; the patent doesn't really mention it. It just seems to cover the good old image includes.
No matter, back when this was patented, this was far from obvious and certainly a novel idea. I am not the biggest fan of software patents, but I'
Re: (Score:2)
I agree that a lot of this was far from obvious when the patent was made. And I agree that this is not a patent troll issue: they actually use the patent, and the patents they've filed seem surprisingly legible. It's not like Microsoft's "57 patent violations by Linux" that they refuse to
Re:It may be obvious but (Score:4, Interesting)
Let's start first with the definition of "obviousness." Patent law doesn't go by the common English or Webster's definitions of the term - it has a very technical meaning, refined by probably a thousand patent law cases. Many nuances. And unhelpfully, the definitive section [uspto.gov] on the topic is circularly defined.
At least two reasons for the technicalities. First, virtually anything is "obvious" in hindsight. Second, what is "obvious" to one (unbiased) person may be completely non-obvious to another (unbiased) person, and the patent office would produce radically inconsistent results if examiners were permitted such subjectivity.
- David Stein
Re: (Score:2)
Everything is obvious (Score:5, Insightful)
The sex and violence of a patent is in the claims. go read em [uspto.gov] and now look at the date the patent was filed: May 19, 1999.. which means it was being written for 6 to 8 months before that. You're saying that rewriting urls in a web page to fetch objects from geographically different servers was obvious in late 1998?
Not defending the patent system in the US or anything, but claiming that something is "obvious" now when the patent was filed in '99 is pretty freakin', well, obvious!
Re:Everything is obvious (Score:5, Insightful)
Yes.
Well, maybe not if you were in high school then. But to people actually doing content delivery over the web, yes. And there were starting to be big web sites around even then.
Re: (Score:3, Insightful)
> from geographically different servers was obvious in late 1998?
Technically, yes. Remember Image bandwidth-stealing? A guy hosting images would find others not only presenting those images in a different website, but to add insult to injury, would load those images from _his_ servers? (i.e. they had modified their IMG tags to load images from the unwitting originator.) Now, if the originating servers were clustered and/or geographicall
Re: (Score:3, Insightful)
Not really. What you describe is basically just offloading static images to an unsuspecting third party. If it's a popular website then t
Re: (Score:3, Interesting)
For examle, if I have a webserver at example.com, and it modifies image URLs within it to point to foo.bar.example.com, and there's an 'example.com' DNS server which contains the NS record
Re: (Score:2)
But, that's pretty damn obvious. Round-robin DNS for load-balancing is an old and obvious technology. Instead of spreading the load in strict order, or by load average, you'd instead uses a lookup table of IPs to physical locations.
And that's pretty trivial. I've seen MUDs in the 80s that knew where you were connecting from.
Caching is "hard", in that hairy issues exist, but simple enoug
Re: (Score:2)
What if the 'unsuspecting third party' was a geographically distributed server setup like CPAN or sourceforge.net?
Nefarious intent does not invalidate prior art.
I have no hassles with Akamai protecting something innovative, say their precise server-determination algorithms, but geographically distributed HTTP load balancing itself is not worth protecting.
Re: (Score:2)
CPAN, SourceForge, etc. don't use DNS load balancing like Akamai does. They just use a collection of static mirrors and they randomly pick one or let you pick from a list. Now if you could just type in "download.sourceforge.net" and have it return a download location logically close to you that would be a different situation. But how would you implement this? If there were hundreds of downlo
Re:Everything is obvious (Score:5, Interesting)
Re: (Score:3, Insightful)
And even so, it is in no way a brilliant idea. I was making web pages with content sucked from multiple sites in 1994, and I was no genius.
It may not be obvious to a non-technical judge or jury, however, even today.
Re: (Score:2)
It may not be obvious to a non-technical judge or jury, however, even today.
Which is really the core of the whole issue, isn't it? Obvious TO WHOM? Under patent law, that "whom" is "a person skilled in the art." In other words, a techie. Now, a lot of techies are vile, petty, competitive creatures with a great disdain for humanity as a whole. For reference, see Slashdot (http://www.slashdot.org/). Of course we are going to find numerous tech professionals who will claim that any damn thing under the Sun
Re: (Score:2)
As to smarter than other techs? Well, there are many people who assume that because they didn't know how to do something it must be black magic. There are others who know, from experience, that there is little you can't do well with a well-intentioned group of smart developers. (Polis
Re: (Score:2)
Re: (Score:2)
Re:Everything is obvious (Score:4, Insightful)
in retrospect.
No it is not, and your hand waving is not helping. The PTO loves to push this self-serving nonsense as if it were fact. People are perfectly capable of evaluating whether something is obvious or not after the fact. They don't mystically lose their intelligence simply because they have more facts at their disposal.
This is obvious, if for no other reason than the HTTP/HTML protocols have built in the ability to get different elements of the one the page from different servers and to URL redirect a client from one server to another plus the address rewriting rules in popular servers like Apache. All of these capabilities existed for years before this "patent". Not to mention DNS referral, caching, network throttling etc. which existed for decades before this "patent". Don't be fooled by patent "claims" which list standard techniques together and then claim the assembly is somehow "different".
Face it, this "patent" is blindingly obvious to anybody with even basic training in networking. The fact that this got through just shows how incompetent the PTO is. Not surprising, given the chutzpah of claiming that the bureaucrats in a small government department can assess against all of human knowledge for whether an idea is original or not. Only a scientist working a life time in a very narrow area can do that and even then they make mistakes.
---
"It is difficult to get a man to understand something when his job depends on not understanding it." - Upton Sinclair
Re:Everything is obvious (Score:4, Insightful)
Re: (Score:2)
Yet nothing about that makes the patent non-obvious to someone in the field, which is how the USPTO is supposed to rate obviousness, not whether the RFC happened to concur with the idea. I specifically remembering thinking that the patent was so bloody obvious that I couldn't believe it had been granted in the first place.
Re: (Score:2)
Actually, around 1998, a DNS server that returned a different IP address for a lookup based on who the request is for was not only novel, it was considered WRONG.
It's just caching at a different network layer. Big deal.
Geographical load balancing was your typical dot-com boom idea.
No it was not. "Geographical load balancing" is just an obfuscated name for "caching", something that had been known about for decades. One of the big problems with the PTO is that they are endlessly confusing invented t
Re: (Score:2)
The facts beg to differ. Research in to negligence cases shows that people are far more likely to rate something as obvious when they've seen the outcome.
I can't remember who defined genius as "The ability to see the obvious things that others miss.", but it's sometimes useful to remember.
Re: (Score:2)
No, I don't think that is what is being said. It was obvious to some people in 1992.
Re: (Score:3, Interesting)
It was already stated that algorithms cannot be patented. And that's all that Akamai se
Re: (Score:3, Interesting)
Re: (Score:2)
By 1996 you could already BUY a system to do it... (Score:5, Interesting)
-Mark Kriegsman
Founder, Clearway Technologies
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
In Akamai's case, there is so little mechanism that they're essentially patenting standard sysadmin tools. Round-robin DNS is an old concept, it usually distributes fairly, or on workload. The only difference in Akamai's case is that it's geographical, and that's just an easy lookup.
Re: (Score:2)
In Akamai's case, there is so little mechanism that they're essentially patenting standard sysadmin tools. Round-robin DNS is an old concept, it usually distributes fairly, or on workload. The only difference in Akamai's case is that it's geographical, and that's just an easy lookup.
I think it's worse than that.
I'm pretty sure that the patents on returning DNS answers based on geography are held by Cisco. Akamai is only claiming the higher level content-management-by-location concept.
I'll admit that, without hindsight, some of this idea is clearly novel. However, the core problem with software patents has never been the novelty or lack of (sometimes there is a lack of novelty, but not always). The core problem is two-fold: 1) software patents are fundamentally math patents, and math i
Re: (Score:2)
Re: (Score:2)
This should be a lesson to us all. If you do something that might be novel - publish, like that you stop someone from patenting the idea and stopping
Non-obviousness (Score:5, Insightful)
Re:Non-obviousness - mod parent up (Score:5, Insightful)
Re: (Score:3, Informative)
Re: (Score:2)
Re: (Score:2)
Just did a report about business patents. Non-obviousness, a requirement of Patents (35 USC 102?), isn't proven by looking at something and saying "Duh!" You need to show prior art preferably enough prior art examples to cover all of Akamai's claims.
I'm not sure that I understand you properly. You are saying that if you can find prior art, this proves obviousness. In other words, the fact that somebody thought of it, makes it obvious, i.e., all things are obvious. Since this is clearly not what you mean
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
So, the first person to do something obvious gets a patent on it?
Apparently the patent system is working as intended, after all.
Technological ignorance in the legal profession (Score:4, Insightful)
Many advertisers will fall fowl of this, since many sites have ad content that is served up by another server which is not their own.
Re: (Score:2)
Re: (Score:2)
Hm (Score:2)
For the small religious subset of Slashdotters... (Score:2)
Re: (Score:2)
Akamai win a dilemma for Microsoft? (Score:2)
Re: (Score:2)
What a ridiculous summary (Score:5, Informative)
READ THE CLAIMS TO FIND OUT WHAT IS BEING COVERED BY THE PATENT!!
Here is claim 1:
1. A distributed hosting framework operative in a computer network in which users of client machines connect to a content provider server, the framework comprising:
a routine for modifying at least one embedded object URL of a web page to include a hostname pretended to a domain name and path;
a set of content servers, distinct from the content provider server, for hosting at least some of the embedded objects of web pages that are normally hosted by the content provider server;
at least one first level name server that provides a first level domain name service (DNS) resolution; and
at least one second level name server that provides a second level domain name service (DNS) resolution;
wherein in response to requests for the web page, generated by the client machines the web page including the modified embedded object URL is served from the content provider server and the embedded object identified by the modified embedded object URL is served from a given one of the content servers as identified by the first level and second level name servers.
Doesn't seem so obvious now, does it?
The second is the fact is that Akamai is a very innovative company that has pioneered a lot of distributed content delivery starting with the early days of the internet. In my mind it is very obvious that they would have a lot of valid patent material. They are most assuredly NOT patent trolls, and in fact have brought many innovations based on some very advanced work to commercial fruition. It is insane that their work is being shown in this light by Slashdot.
The company was founded by an MIT graduate student (Dan Lewin) and an applied math professor from MIT, Tom Leighton who is currently head of the algorithms group at at MIT's Computer Science and Artificial Intelligence Laboratory. Lewin was tragically killed when AA flight 11 was crashed during the 9-11 terrorist attack.
This article is one of the most ridiculous ever posted by Slashdot.
Re: (Score:3, Insightful)
You know what your quote says: "serve some of the parts of a webpage from other servers." In other words if you allow an easy way of hot linking of images then you meet the criteria.
Re: (Score:3, Funny)
Re: (Score:2)
It may or may not be innovative in terms of web caching however in that case their patent doesn't seem to be of much practical use. In fact since if you regard THAT as their chief innovation you must have a very low opinion of their ingenuity.
See i
Re: (Score:2)
Re: (Score:2)
You'd be "surprised", i.e. you don't know for sure.
Yet I'm right and you're not, so apparently you didn't know. I on the other hand know I'm clever and usually right but don't claim to unless I'm sure, such as right now. United States Patent 5752022 filed in 1995 by IBM which mentions URL prepending in a distributed network.
A simple search of the patent database will probably find hundreds of similar patents and many are probably earlier, I'm sure the original prior art can be traced to the beginnings of the URL scheme. It's obvious, only a zealot would th
Re: (Score:2)
The DNS aspect of this patent and how it's used is key from what I understand of a quick look at prior court cases, the rest of it is in many ways fluff (prior art and so on I think).
If you're going to argue something is non-obvious then at least know the bloody subject and how it's actually BEEN argued to be no
Re:What a ridiculous summary (Score:5, Insightful)
READ THE CLAIMS TO FIND OUT WHAT IS BEING COVERED BY THE PATENT!!
Re:What a ridiculous summary (Score:5, Insightful)
All I'm seeing is the same thing as the summary, just with more words.
If you think this is the sort of thing that needs patent protection, you are high; no matter how many "wherein"'s they throw in there.
I'm sure they are in fact a very innovative company, that doesn't stop this patent from being complete bullshit.
Re: (Score:2)
The patent is actually kinda obvious, actually actually. Whether it was obvious in 1999 when it was registered is another matter, but distributed content serving is certainly quite obvious now. Also, whether or not they're an innovative company is irrelevant if they're suing another company for infringing on their (obvious or not) patent specifically to stop them competing. That's the very definition of anti-competitive behavior, even if it's legally allowed.
please no
Re: (Score:2)
Does, too.
1998 was hardly the early days of the Internet. Or even the Web, really, although that's debatable enough.
I'm not sure what Lewin's death has t'do with patent rights.
Trouble for other players? (Score:2, Interesting)
It'll also be very interesting to see how the other well-funded CDN players react to this - Level 3 (
So they've patented (Score:5, Interesting)
Brilliant!
What a novel use of technology.
Surely this is just amazing. Who ever woulda thunk that computers could do things for us automatically?
Re: (Score:2)
You aren't anti-American, are you n6kuy?
Talk too much, know too little... (Score:3, Insightful)
First, the patent isn't so obvious. The patent is for Edge Side Includes, which is in no way trivial. It is the method by which you can have a full HTML page (eg.the slashdot homepage), cached at the akamai edge servers, and have one part of personalized message (welcome USERNAME / you have X private messages / etc. etc.) load from the origin servers, taking into account all cookies etc. Doing so required inventing a whole new method of writing, interpreting, and selectively applying caching to enhanced include tags, that too across a distributed network, supporting other cool items like tiered distribution, progressive caching, server side cookies etc. etc.
Now, realize, this isn't about loading one object, like an image / flash object / javascript from a different server, but transparently loading a part of the core HTML code of a page from the origin server, with full support for cookies / post etc. while making it look like it is coming from the same physical source, so as to maintain cookie coherency. Trust me, before Akamai's founder came around and invented this, web caching static objects with personalized items was like pulling teeth. Also, Akamai is licensing this technology to the whole world http://www.akamai.com/html/support/esi.html [akamai.com], and if they choose not to license this to their competitors, but the competitor goes ahead and implements it "as-is" based on their spec, then hey, the competitor deserves to be sued.
And you know what? Limelight is a bunch of ex-akamai guys, who left with a boatload of trade secrets, and customer lists. I got a call from them within 15 days of their service starting, asking to switch over at half price, but their Super POP model doesn't work for dynamic content like ours.
Re: (Score:3, Insightful)
That almost makes sense, except that even according to the Akamai page you link to...
Nothing to see here (Score:2)
I'll stand up for Akamai (Score:5, Interesting)
Limelight copied akamai's patented edge cache implementation, and violated enough of the patent to warrant this decision.
I can see how a bunch of people jump on the "obvious" bandwagon, developing an edge cache for a single enterprise would be relatively easy to do. Developing an edge cache infrastructure that will work across hundreds and thousands of different enterprises with different business and process infrastructures with varying and often conflicting traffic load patterns is an entirely different problem.
Let's look at the url rewriting aspect of it. The rewritten urls are specified to include popularity flag and use virtual hosts as a serial #. Something that would be obvious today, but in '98/'99 not so much.
Let's look at geographic dispersion. What is your obvious geographic dispersion methodology? A database like MaxMind has to offer? Those were few and far between in 1999. They use a network map. Further, they also consider the load of their servers when returning dns responses - so we're not just talking about getting the closest server to the edge, we're talking about getting the closest server with the lowest load at the edge. There's also the problem that the dns request is in most cases not coming from the client machine, but from a geographically disparate dns cache. The akamai system redirects users to a closer server if one exists and that situation is discovered by the web server.
There's also the situation that the network load of a particular server becomes too heavy while serving a particular request midstream (i.e. for audio and video). This patent covers switching the responsibility for handling a request to another server midstream.
This patent also includes anti-DOS/DDOS technology - a no brainer today, but in 1999? Not so much.
I wouldn't categorize Akamai as good or bad. I don't know much about the company itself. I can see the possibility of working around their patent to build a competitor - it's not an all-inclusive-only-we-can-do-CDN patent. But given the fact that limelight's foundation was built by a bunch of Akamai's ex-employees, it certainly isn't surprising that they chose the same path for resolving issues that Akamai did. And given Limelight's close ties with Microsoft, it's also not very surprising that they chose to emulate what they knew rather than innovating and improving upon the model.
in other news (Score:2)
Re: (Score:3, Informative)
Re: (Score:2)
Re:Akamai != Squid (Score:2)