Ports Search

XML-DBMS is middleware for transferring data between XML documents and relational databases. It views the XML document as a tree of data-specific objects in which element types are generally viewed as classes and attributes and PCDATA as properties of those classes. It then uses an object-relational mapping to map these objects to the database. An XML-based mapping language is used to define the view and map it to the database.

The SRU package provides a framework for working with the Search and Retrieval by URL (SRU) protocol developed by the Library of Congress. SRU defines a web service for searching databases containing metadata and objects. SRU often goes under the name SRW which is a SOAP version of the protocol. You can think of SRU as a RESTful version of SRW, since all the requests are simple URLs instead of XML documents being sent via some sort of transport layer.

phpMyFAQ is a multilingual, completely database-driven FAQ-system. It supports various databases to store all data, PHP 4.1.0 (or higher) is needed in order to access this data. phpMyFAQ also offers a Content Management-System with a WYSIWYG editor and an Image Manager, flexible multi-user support with LDAP support, a news-system, user-tracking, language modules, enhanced automatic content negotiation, templates, extensive XML-support, PDF-support, a backup-system and an easy to use installation script.

Filebench is quick to set up and use unlike many of the commercial benchmarks which it can emulate. It is also a handy tool for micro-benchmarking storage subsystems and studying the relationships of complex applications such as relational databases with their storage without having to incur the costs of setting up those applications, loading data and so forth. Filebench uses loadable workload personalities in a common framework to allow easy emulation of complex applications upon file systems. The workload personalities use a Workload Definition Language to define the workload's model.

Boulder IO is a simple TAG=VALUE data format designed for sharing data between programs connected via a pipe. It is also simple enough to use as a common data exchange format between databases, Web pages, and other data representations. The basic data format is very simple. It consists of a series of TAG=VALUE pairs separated by newlines. It is record-oriented. The end of a record is indicated by an empty delimiter alone on a line. The delimiter is "=" by default, but can be adjusted by the user.

The ultimate replacement for spreadsheets, mind mappers, outliners, PIMs, text editors and small databases. Suitable for any kind of data organization, such as Todo lists, calendars, project management, brainstorming, organizing ideas, planning, requirements gathering, presentation of information, etc. It's like a spreadsheet, immediately familiar, but much more suitable for complex data because it's hierarchical. It's like a mind mapper, but more organized and compact. It's like an outliner, but in more than one dimension. It's like a text editor, but with structure.

The Calibrator is a small C program that is supposed to analyze a computer's memory system and extract the following parameters: * number of cache levels * for each cache level: size, linesize, access/miss latency * main memory access latency, number of TLB levels * for each TLB level: capacity, pagesize, TLB miss latency The Calibrator is a by-product of our work on Main-Memory Databases within the Monet project. The Calibrator is freely available for download and usage, but we kindly ask all users to include a reference to the Calibrator's home page whenever they refer to the Calibrator or publish calibration results.

This driver uses a database table to store the cache for CHI. The newest versions of MySQL and SQLite are known to work. Other RDBMSes should work. Why cache things in a database? Isn't the database what people are trying to avoid with caches? This is often true, but a simple primary key lookup is extremely fast in many databases and this provides a shared cache that can be used when less reliable storage like memcached is not appropriate. Also, the speed of simple lookups on MySQL when accessed over a local socket is very hard to beat. DBI is fast.

Celery is an open source asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes. Tasks can execute asynchronously (in the background) or synchronously (wait until ready). Celery is written in Python, but the protocol can be implemented in any language. It can also operate with other languages using webhooks. The recommended message broker is RabbitMQ, but limited support for Redis, Beanstalk, MongoDB, CouchDB, and databases (using SQLAlchemy or the Django ORM) is also available.

The OpenChange MAPI library aims to provide interoperability with an Open Source implementation of Microsoft Exchange protocols under UNIX/Linux. The current implementation offers a client-side library which can be used in existing messaging clients and offer native compatibility with Exchange Servers up to 2007. MAPI stands for Messaging Application Programming Interface and is used in the Microsoft Exchange Server groupware server. This solution works with Outlook and provides collaborative features such as a messaging server, shared calendars, contact databases, public folders and tasks.