Current status of the Malete engine.
The 1.0 release is available for
This is probably also the last release of the malete project as such,
as basically all goals have been achieved.
The follow-up is the Selene project,
featuring a wider range of supported data structures and builtin
| what 1.0 contains |
- malete server
communicating over TCP or UNIX sockets as described in the
- multi process server option
(on systems with working fork and fcntl, i.e. not on windows)
- search expressions
and a single '?' to retrieve record contents as described in the
- sample client interface
in PHP and possibly other languages
- conversion tools
from and to
traditional CDS/ISIS, IIF (ISO 2709) and plaintext
- stable small file formats as
(32 bit file access using 8 byte pointers)
- collation support
is working as specified in
character set support
| what 1.0 does not contain |
(at least not officially)
- protocol features marked as optional extensions
- record filtering
since that is rarely used and can be done at application level
- large files and key compression
- any promise on the C API
(it IS going to change)
- the Malete object model
definitively needs some more tweaking before being ready for prime time
| what is still TO DO |
- de/serializing of records to/from files accessed in a stream like fashion
needs to be debugged, unified and heavily tested.
The concept of a sink probably needs to be straightened out.
- the single process server should do proper session switching.
Every session should have a separate input buffer.
On the other hand, we may also dump single process completely.
- both single process and multi process server need heavy testing
$Id: Status.txt,v 1.4 2005/02/23 17:08:00 kripke Exp $