CloudVZ CDN supports HTTP push, which ensures that content is distributed proactively to your customer's chosen CDN locations.
Your customer (e.g. a website owner or content publisher) uploads their content to a CDN Storage server, from where it is pushed to other sites on the CDN. HTTP Push is particularly useful for larger files such as software installers and patches, that would take longer to download from a distant location. Push is normally recommended where file sizes are larger than 50MB.
CloudVZ CDN also supports HTTP Pull, which ensures that content is distributed to a specific CDN location when a user requests it.
Your customer (e.g. a website owner) stores content on their origin server, and rewrites URLs to include a subdomain (e.g. cdn.yourcompany.com). When content is requested by an end user, it's pulled to the CDN from the origin server, and delivered to the closest location to the user requesting it.
Push is more suited to smaller file sizes, where the time taken to retrieve the original file will not be particularly noticeable. Customers can also set up alternative pull locations in case the origin server is unavailable.
CloudVZ CDN supports caching of static and dynamic content on edge servers at any CloudVZ CDN location. HTTP caching offloads web content onto the CloudVZ CDN network, and ensures it is delivered faster by storing a copy of the content at the network edge, closer to the end user.
Prefetching content ensures files are already at an end user's closest edge server when they request a piece of content. It's particularly useful for large files. CloudVZ CDN allows you to prefetch content and pre-populate it to your chosen CDN locations.
Purging also helps to ensure that edge servers are serving the latest content. CloudVZ CDN makes it easy to purge files from your CDN - for example, to ensure that banner ads are refreshed on time for the launch of a new sales campaign.