Ports Search

The ht://Dig system is a complete world wide web indexing and searching system for a domain or intranet. This system is not meant to replace the need for powerful internet-wide search systems like Yahoo! or Google. Instead it is meant to cover the needs for a single company, campus, or even a sub section of a web site. As opposed to some WAIS-based or web-server based search engines, ht://Dig can span many web servers as long as they all understand the HTTP 1.0 protocol.

Full-text search system. You can search lots of documents for some documents including specified words. If you run a web site, it is useful as your own search engine for pages in your site. Also, it is useful as search utilities of mail boxes and file servers. The characteristic of Hyper Estraier is the following. * High performance of search * High scalability of target documents * Perfect recall ratio by N-gram method * Phrase search, attribute search, and similarity search * Multilingualism with Unicode * Independent of file format and repository * Simple and powerful API * Supporting P2P architecture

Rarian is designed to be a replacement for scrollkeeper. It is currently undergoing heavy development. As of writing, rarian can be installed in place of scrollkeeper and everything will work okay. Rarian manages documentation metadata (as specified by the Open Source Metadata Framework (OMF) and provides a simple API to allow help browsers to find, sort, and search the document catalog. It will also be able to communicate with catalog servers on the Net to search for documents which are not on the local system.

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.) Preliminary tests show boa is about twice as fast as Apache, and is capable of handling 50 hits per second on a 66 MHz '486. The primary design goals of Boa are speed and security. Security, in the sense of "can't be subverted by a malicious user", not "fine grained access control and encrypted communications".

fcgiwrap is a simple server for running CGI applications over FastCGI. It hopes to provide clean CGI support to Nginx (and other web servers that may need it). Features: * very lightweight (84KB of private memory per instance) * fixes broken CR/LF in headers * handles environment in a sane way (CGI scripts get HTTP-related env. vars * from FastCGI parameters and inherit all the others from fcgiwrap's * environment) * no configuration, so you can run several sites off the same fcgiwrap pool * passes CGI stderr output to fcgiwrap's stderr (this is by design but * stderr could be also passed to FastCGI stderr stream)

Google App Engine software development kit (SDK). Google App Engine enables you to build web applications on the same scalable systems that power Google applications. Google App Engine applications are implemented using the PHP or the Python programming language. The runtime environment includes the full Python language and most of the Python standard library. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. With App Engine, there are no servers to maintain: you just upload your application, and it's ready to serve your users.

The htt provides a large variety of HTTP-related functionality, useful for implementing all kinds of HTTP-based tests: - Advanced HTTP protocol handling, including ne-grained timeout handling, request and response validation - Simulating clients and servers, including startup and shutdown of server daemons. This allows to create mock-ups of back-end systems in more complex test situations, for example when the tested application needs to interact with a 3rd-party back-end system which is not available in the testing environment. - Execution of external commandline tools, using their output as request or response data, or for validation purposes. - Copying stream data (e.g. from a response) and re-using it in variables.

Emplacken is a tool for managing a set of Plack applications based on config files. It also adds support for privilege dropping and error logs to those Plack servers that don't support these features natively. It works be reading a config file and using that to generate a PSGI application file based on your config. It knows how to generate Catalyst, Mojo, and Mason app files natively. For other apps, or more complicated setups, you can supply a template to Emplacken and it will use that to generate the PSGI app.

HTTPD-User-Manage is set of Perl modules for managing access control with the Apache, NCSA httpd, CERN and Netscape servers (and maybe some others). You can install this program as a CGI script to allow remote users to change their Web access passwords. Web administrators can use it to remotely add, edit and delete users and their groups. You can also use it from the command line as a nice all-in-one interface to access control databases based on text files, DBM files, and SQL databases.

STF::Dispatcher::PSGI implements the basic STF Protocol (http://stf-storage.github.com) dispatcher component. It does not know how to actually store or retrieve data, so you must implement that portion yourself. The reason this exists is mainly to allow you to testing systems that interact with STF servers. For example, setting up the main STF implementation is quite a pain if all you want to do is to test your application, but with this module, you can easily create a dummy STF dispatcher.