30.07.2012 Views

Reference Guide

Reference Guide

Reference Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Zend Download Server<br />

This component is not relevant for Windows and IBM i Servers.<br />

Zend Server <strong>Reference</strong> Manual<br />

The ZDS (Zend Download Server) component improves Apache's scalability by taking over static content<br />

downloads and passing them to a dedicated process that is optimized for parallel downloads (not<br />

supported on Windows servers).<br />

The ZDS enhances Apache's static download capabilities. This releases Apache processes to handle<br />

more dynamic requests. There are two ways to define which files will be serviced by the ZDS: Either via<br />

the API or via an external configuration file (mime_types).<br />

A single ZDS process can handle substantially more concurrent downloads, compared to Apache's<br />

capabilities.<br />

The Zend Download Server is a PHP extension that forks an HTTP server separate from Apache to be<br />

used for serving large files of given types by redirecting regular requests from your Apache to a separate<br />

server.<br />

The Zend Download Server is a PHP extension that forks an HTTP server (separate from Apache) to<br />

serve specific types of large files, by redirecting regular requests from your Apache to a separate server.<br />

The Zend Download Server offloads the limited Apache process activity to avoid the situation where a<br />

connection is open for a long time to serve large downloads, which in turn prevents the Apache from<br />

serving requests that can be handled immediately. The concept is similar to the express lane in a<br />

supermarket: A separate "lane" is made available for large downloads, which frees up the other lanes for<br />

smaller downloads.<br />

Based on the settings in the mime_types file, specific file extensions are immediately identified when the<br />

request is received: These downloads are rerouted to a separate server.<br />

This essentially creates a separate process which functions as an HTTP daemon, dedicated to<br />

downloads.<br />

The mechanism is a PHP extension that creates a daemon to handle the rerouting when the extension<br />

loads. We also provide a mime_types file and an API for explicitly directing content (a file or buffer) to be<br />

handled by the ZDS (in parallel to using the mime_types file, depending on your preferences).<br />

197

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!