Free apache software for linux

Jakarta Projects goal is to provide commercial-quality server solutions based on the Java Platform that are developed in an open and cooperative fashion.

Tomcat 3.x is an implementation of the Java Servlet 2.2 and JavaServer Pages 1.1 Specifications.

Tomcat 4.x is an implementation of the Java Servlet 2.3 and JavaServer Pages 1.2 Specifications, and is a re-implementation of the Tomcat servlet engine from the ground up.

Apache Xindice is a database designed from the ground up to store XML data or what is more commonly referred to as a native XML database. The name is pronounced zeen-dee-chay in your best faux Italian accent. Dont worry if you get it wrong though, we wont mind. We just care that you spell it correctly.
You might be wondering what a native XML database is good for? Well it pretty much has one purpose, storing XML data. If you dont have any XML data, dont want any XML data or think XML is the most over-hyped technology of the new millennium, then Xindice is not for you. Were not out to change the way data in general is stored, only to provide a good solution for storing XML data. If you survey your projects and see XML popping out of every corner, then Xindice might be a real help for storing that XML.
The benefit of a native solution is that you dont have to worry about mapping your XML to some other data structure. You just insert the data as XML and retrieve it as XML. You also gain a lot of flexibility through the semi-structured nature of XML and the schema independent model used by Xindice. This is especially valuable when you have very complex XML structures that would be difficult or impossible to map to a more structured database.
At the present time Xindice uses XPath for its query language and XML:DB XUpdate for its update language. We provide an implementation of the XML:DB API for Java development and it is possible to access Xindice from other languages using built in XML-RPC API. As standards in the XML database area mature Xindice will include support for those that are most important.
Xindice is the continuation of the project that used to be called the dbXML Core. The dbXML source code was donated to the Apache Software Foundation in December of 2001.
Native XML database technology is a very new area and Xindice is very much a project still in development. The server currently supports storing well formed XML documents. This means it does not have any schema that constrains what can be placed into a document collection. This makes Xindice a semi-structured database and provides tremendous flexiblity in how you store your data, but, also means you give up some common database functionality such as data types. In its current state Xindice is already a powerful tool for managing XML data. However, there is still much that needs to be done. Feedback and contributions are actively encouraged.
This document attempts to describe those features that are working and can be used today. You should review the README file that is part of the Xindice distribution for the most current status on the project.
Main features:
- Document Collections: Documents are stored in collections that can be queried as a whole. You can create collections that contain just documents of the same type or you can create a collection to store all your documents together. The database doesnt care.
- XPath Query Engine: To query the Document Collections you use XPath as defined by the W3C. This provides a reasonably flexible mechanism for querying documents by navigating and restricting the result tree that is returned.
- XML Indexing: In order to improve the performance of queries over large numbers of documents you can define indexes on element and attribute values. This can dramatically speed up query response time.
- XML:DB XUpdate Implementation: When you store XML in the database you may want to be able to change that data without retrieving the entire document. XUpdate is the mechanism to use when you want to do server side updates of the data. It is an XML based language for specifying XML modifications and allows those modifications to be applied to entire document collections as well as single documents.
- Java XML:DB API Implementation: For Java programmers Xindice provides an implementation of the XML:DB API. This API is intended to bring portability to XML database applications just as JDBC has done for relational databases. Most applications developed for Xindice will use the XML:DB API.
- Command Line Management Tools: To aid the administrator Xindice provides a full suite of command line driven management tools. Just about everything you can do through the XML:DB API can also be done from the command line.
- Modular Architecture: The Xindice server is constructed in a very modular manner. This makes it easy to add and remove components to tailor the server to a particular environment or to embed it into another application.
- Database Structure
- The Xindice server is designed to store collections of XML documents. Collections can be arranged in a hierarchy similar to that of a typical UNIX or Windows file system.
- In Xindice the data store is rooted in a database instance that can also be used as a document collection. This database instance can then contain any number of child collections. In a default install of Xindice the database instance is called db and all collection paths will begin with /db. It is possible to rename the database instance if desired though it is not necessary to do so.

The Apache::FileManager module is a simple HTML file manager. It provides file manipulations such as cut, copy, paste, delete, rename, extract archive, create directory, create file, edit file, and upload files.
It also has the ability to rsync the server htdocs tree to another server with the click of a button.
Enhancements:
- prevented file edit screen from opening when cancel is clicked when creating new filenames
- fixed up documentation

Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process.

Apache DSSI is a SSI extention for calling Dynamic function.

By using this extentions to mod_include, you can make your own function for SSI (Server Side Includes) and you can call your function with SSI directives. This solution is based on mod_so and mod_include. By using DSSI, you can integrate your CGI easily and make your CGI faster than any other CGI accelerator.

Installation:

Download and compile Apache 1.3.X
Simply download dssi_1.0.0.tar.gz
Unzip and untar.
Replace apache_1.3.X/src/modules/standard/mod_include.c with this mod_include.c
Configure.
./configure --enable-module=include
If your binary type is ELF,
LDFLAGS="-export-dynamic" ./configure --enable-module=include
Compile and install apache.

Enabling DSSI

By using LoadDSSI directive, you can load your dynamic functions. Later one override earlier ones. It means, you can only call functions of the last one with DSSI directive.

AddType text/html .shtml
AddHandler server-parsed .shtml
LoadDSSI libexec/dssi_util.so
LoadDSSI libexec/dssi.so

Apache mod_suid allows per-vhost execution of scripts under their own UIDs. It functions in a way similar to Apaches perchild MPM, but differs in a number of ways.

Apache mod_suid does per child user/group switching; the Apache MPM makes switches based on vhosts. All processing is done under a specific UID/GID, including PHP and mod_perl scripts.

Apache::MP3 is a Perl module that can generate streamable directories of MP3 and Ogg Vorbis files.

SYNOPSIS

# httpd.conf or srm.conf
AddType audio/mpeg mp3 MP3
AddType audio/playlist m3u M3U
AddType audio/x-scpls pls PLS
AddType application/x-ogg ogg OGG

# httpd.conf or access.conf
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3
< /Location >

# Or use the Apache::MP3::Sorted subclass to get sortable directory listings
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Sorted
< /Location >

# Or use the Apache::MP3::Playlist subclass to get persistent playlists
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Playlist
< /Location >
A demo version can be browsed at http://www.modperl.com/Songs/.

This module makes it possible to browse a directory hierarchy containing MP3, Ogg Vorbis, or Wav files, sort them on various fields, download them, stream them to an MP3 decoder like WinAmp, and construct playlists. The display is configurable and subclassable.

NOTE: This version of Apache::MP3 is substantially different from the pre-2.0 version described in The Perl Journal. Specifically, the format to use for HREF links has changed. See Linking for details.

Appctl is a framework for virtually any server software. It provides a central script called "ctl" which allows you to start, stop, restart, maintain, or query the current status of an application.
Appctl is meant as a completely generic replacement for application-specific startup/stop scripts. The project also supplies generic monitoring scripts for clusters, which can dramatically decrease clustering costs.
Enhancements:
- This release includes configuration files for running the Apache Web server with integrated appctl support.