Php ftp script

Apache 2.0

One of open-source's quiet success stories, the Apache Web server stands behind more than 60 percent of all domains, according to the Netcraft Web Server survey (www.netcraft.com). ISPs and Web-hosting companies often turn to Apache because of its support for numerous platforms, easily implemented virtual hosting capabilities, and add-on modules that extend its capabilities. But there's always room for improvement, and six years after Apache's initial release, the community is readying Version 2.0. The update is still several months from release, so we don't yet know how it will stack up against its competition, but our first glimpse shows a promising follow-up to a popular server.

The real differences in Apache 2.0 lurk under the hood. Whereas previous versions were designed primarily for Unix and thus relied on an emulation layer when run on Windows, Apache 2.0 is operating systemneutral. The new Apache Portable Runtime (APR) optimizes capabilities such as process management for each operating system yet lets the Web server itself ignore platform-specific distinctions. Apache developers claim this will improve the performance and stability of the Windows implementation by eliminating the emulation layer. Furthermore, the APR is accessible to Web developers writing cross-platform programs in C, which is faster than interpreted languages such as Perl and PHP that are often used for Web development.

Additionally, the server itself is protocol-independent; although it's primarily an HTTP (Web) server, it's also designed to support alternative protocols such as FTP. Such a design should simplify administration and reduce security risks.

Apache 2.0 also simplifies dynamically generating some types of content that the previous version stumbled on. In the past, for example, server-side include (SSI) directives couldn't be included in Web pages generated dynamically by a CGI script; the developer had to choose one approach or the other or work around the problem by writing more complex code that directly accessed the Apache API. With Apache 2.0, we were able to create simple scripts that emitted SSIsa technique that could help reduce site developers' workloads.

At the interface level, the changes are hard to detect. We were able to plug an Apache 2.0 beta into a development site running a stable release of Apache (1.3.17) and immediately serve up pages, run scripts, and connect to databases. Editing text files is still the only way to manage configuration, although third-party graphical front ends are available.

Part of Apache's lasting appeal has been its versatility. Its open API lets developers write add-on modules that change its behavior: If the server lacks a function that a site needs, chances are there's a plug-in module available. New modules for Apache 2.0 support enhanced caching capabilities and improved multilingual support.