With LimelightDELIVER, you can host content on our servers or your servers. When you choose Limelight Networks as the origin, our proprietary network ensures that every delivery of every title happens at lightning speed and with zero network misses. Your audiences will enjoy superfast access, since most content is served directly to their broadband networks. And of course, you’ll avoid the costs of managing your own CDN infrastructure. To transfer content from your servers to ours, you have a choice of upload methods, including HTTP, FTP, sFTP, and Aspera, depending on your security and performance requirements. |
| |
 |
| Fig1. View geographic information in a selection of table and map formats. |

You need data to analyze your operations. How many bits were delivered? How much bandwidth did your content consume? How many users did you serve and what files did they download? What is the relative popularity of each title? A flexible customer portal called LimelightEXCHANGE makes it easy to monitor every aspect of your content delivery. You can also request raw logs every 24 hours or live logs every 15 minutes, both delivered in industry-standard format. For businesses that demand even more information, Limelight Networks also offers LimelightEXCHANGE Premium. This enhanced service level includes new features -- such as geo reporting, web performance measurement, and self-ordering -- giving you greater insight into your content delivery operations. |
| |

Advanced management tools enable you to control how LimelightDELIVER publishes your content. For example, you can choose the progressive download option if you want to permit multiple views and opens — perfect for video rentals, PDFs, or software demos. Want to give your users the flexibility to skip through your Flash Video files and start playing wherever they like? With FLV Seek, the download can start from any point your users choose, so they enjoy faster access to the content they want and you pay for a smaller download.
In customer-origin configurations, the Headers feature enables you to set business rules for how long your files remain in cache on our CDN, especially useful for highly volatile content. Since the Header settings are on your server, you're always in control. To maintain content freshness or for managing exceptions, the Purge Utility allows authorized individuals to delete content cached across our CDN. And with the Geo Compliance option, you can ensure that your content is not accessible outside of a defined geographic area, ideal for managing media licenses with geographic restrictions.
|
| |

With our MediaVault option, your website generates a unique time-based URL to your content each time it's requested by your visitors. Because the URL expires within minutes, your content and your bandwidth are protected from abuse by spiders, bots, and deep linking. Even if another site were to embed the link, it would no longer be functional — preventing others from publishing your content without paying for its delivery.
MediaVault allows you to set start and stop dates/times, perfect for time-sensitive content. And since each URL is unique to each user request, it can't be copied and emailed to unauthorized individuals. You can also limit access to a clock of IP addresses. Best of all, MediaVault controls don't result in server latency, thanks to a token-based system that avoids unwanted three-way handshakes, common to other methods of authentication. |
| |

Limelight Networks makes it easy to add user-generated content to your sites in your choice of major media formats, including Windows Media, Flash, RealPlayer, QuickTime, and 3GPP. Starting with your source content, simply define your workflow: choose your encoding/transcoding profile, specify one or more target formats, set the bit rate, and specify the destination sites or devices — and your media is transformed and published automatically. As part of the workflow, you can also generate thumbnails, create titles, or add watermarks to your video content. Customize the included workflow templates, or build your own. |
| |
| * Range requests require that the full file is cached at the edge. |
|