John Kloninger - Cambridge MA, US David Shaw - Newton MA, US
International Classification:
G06F015/16
US Classification:
709/200000
Abstract:
An enterprise content delivery network includes two basic components: a set of content servers, and a central controller for providing coordination and control of the content servers. The central controller coordinates the set of distributed servers into a unified system, for example, by providing provisioning, content control, request mapping, monitoring and reporting. Content requests may be mapped to optimal content servers by DNS-based mapping, or by using a policy engine that takes into consideration such factors as the location of a requesting client machine, the content being requested, asynchronous data from periodic measurements of an enterprise network and state of the streaming media servers, and given capacity reservations on the enterprise links. An ECDN provisioned with the basic components facilitates various customer applications, such as one or more of the following: live, corporate, streaming media (internal and Internet sources) and HTTP content delivery.
Content Delivery Network (Cdn) Content Server Request Handling Mechanism With Metadata Framework Support
John Josef Kloninger - Cambridge MA, US Mark C. Nottingham - Melbourne, AU David R. Karger - Cambridge MA, US Philip A. Lisiecki - Milton MA, US
International Classification:
H04L 29/12
US Classification:
709217
Abstract:
To serve content through a content delivery network (CDN), the CDN must have some information about the identity, characteristics and state of its target objects. Such additional information is provided in the form of object metadata, which according to the invention can be located in the request string itself, in the response headers from the origin server, in a metadata configuration file distributed to CDN servers, or in a per-customer metadata configuration file. CDN content servers execute a request identification and parsing process to locate object metadata and to handle the request in accordance therewith. Where different types of metadata exist for a particular object, metadata in a configuration file is overridden by metadata in a response header or request string, with metadata in the request string taking precedence.
Internet Content Delivery Service With Third Party Cache Interface Support
Daniel M. Lewin - Cambridge MA, US Bruce Maggs - Pittsburgh PA, US John Josef Kloninger - Cambridge MA, US
Assignee:
Akamai Technologies, Inc. - Cambridge MA
International Classification:
G06F 15/167
US Classification:
709217, 711122
Abstract:
Third party cache appliances are configured into a content delivery service to enable such devices to cache and serve content that has been tagged for delivery by the service. The invention enables the content delivery service to extend the reach of its network while taking advantage of high performance, off-the-shelf cache appliances. If the third party caches comprise part of a third party content delivery network, the interconnection of caches to the CDS according to the present invention enables the CDS and the third party network to share responsibility for delivering the content. To facilitate such “content peering,” the CDS may also include a traffic analysis mechanism to provide the third party network with preferably real-time data identifying the content delivered by the CDS from the third party caches. The CDS may also include a logging mechanism to generate appropriate billing and reporting of the third party content that is delivered from the cache appliances that have been joined into the CDS.
Content Delivery Network (Cdn) Content Server Request Handling Mechanism With Metadata Framework Support
- Cambridge MA, US John Josef Kloninger - Cambridge MA, US Mark C. Nottingham - Melbourne, AU David R. Karger - Cambridge MA, US Philip A. Lisiecki - Milton MA, US
International Classification:
H04L 29/12 H04L 29/08 H04L 29/06
Abstract:
To serve content through a content delivery network (CDN), the CDN must have some information about the identity, characteristics and state of its target objects. Such additional information is provided in the form of object metadata, which according to the invention can be located in the request string itself, in the response headers from the origin server, in a metadata configuration file distributed to CDN servers, or in a per-customer metadata configuration file. CDN content servers execute a request identification and parsing process to locate object metadata and to handle the request in accordance therewith. Where different types of metadata exist for a particular object, metadata in a configuration file is overridden by metadata in a response header or request string, with metadata in the request string taking precedence.
Content Delivery Network (Cdn) Content Server Request Handling Mechanism With Metadata Framework Support
- Cambridge MA, US John Josef Kloninger - Cambridge MA, US Mark C. Nottingham - Melbourne, AU David R. Karger - Cambridge MA, US Philip A. Lisiecki - Milton MA, US
International Classification:
H04L 29/12 H04L 29/06 H04L 29/08
Abstract:
To serve content through a content delivery network (CDN), the CDN must have some information about the identity, characteristics and state of its target objects. Such additional information is provided in the form of object metadata, which according to the invention can be located in the request string itself, in the response headers from the origin server, in a metadata configuration file distributed to CDN servers, or in a per-customer metadata configuration file. CDN content servers execute a request identification and parsing process to locate object metadata and to handle the request in accordance therewith. Where different types of metadata exist for a particular object, metadata in a configuration file is overridden by metadata in a response header or request string, with metadata in the request string taking precedence.
Youtube
"God as a Party Host" God Views Video Curricu...
Go to WWW.RENOVARE.US to purchase. Chapter 6 on "God as a Party Host" ...