mod_dav enables Apache to understand the WebDAV protocol (extensions to HTTP). WebDAV stands for "Web-based Distributed Authoring and Versioning", and is defined by RFC 2518. WebDAV is intended to replace proprietary authoring protocols such as those used by Frontpage or NetObjects' Fusion, but is also a complete set of protocols for manipulating a webserver's files and directories, and their properties.
The Apache/Perl integration project brings together the full power of the Perl programming language and the Apache HTTP server. With mod_perl it is possible to write Apache modules entirely in Perl. In addition, the persistent interpreter embedded in the server avoids the overhead of starting an external interpreter and the penalty of Perl start-up time.
Web500gw expects HTTP requests from a WWW browser on a TCP port (usually 8888). Depending on the requested URL, web500gw performs read/search/modify/add/delete requests to the Directory and sends HTML pages back to the browser. Web500gw uses the LDAPv2 protocol to talk to a Directory server. It is able to work with a Standalone LDAP server (like UMich/OpenLDAP slapd or Netscape LDAP product) and with an LDAP Frontend to an X.500 Directory System Agent.
Plucker is an offline Web and eBook viewer for Palm OS-based handheld devices and PDAs. It comes with Unix/Linux tools and conduits, and Windows and Mac OS X conduits that let you decide exactly what part of the Web you want to view on your PDA (as long as it's in standard HTML or text format). The requested Web pages are processed, compressed, and transferred to the PDA for viewing by the Plucker viewer.
Jigsaw is W3C's leading-edge Web server platform, providing a sample HTTP 1.1 implementation based on RFC2616 and a variety of other features on top of an advanced architecture implemented in Java. Jigsaw provides both client and server HTTP/1.1 implementations, is fast, easy to extend, flexible, and is also packaged as a ready-to-run HTTP/1.1 proxy-cache.
Boa is a single-tasking HTTP server. That means that unlike traditional Web servers, it does not fork for each incoming connection, nor does it fork many copies of itself to handle multiple connections. It internally multiplexes all of the ongoing HTTP connections, and forks only for CGI programs (which must be separate processes), automatic directory generation, and automatic file gunzipping. Tests show boa is capable of handling up to several hundred hits per second on a 100 Mhz Pentium, dozens of hits per second on a lowly 20 MHz 386/SX, and thousands on more powerful CPUs.