Free history of communications software for linux

Ice, the Internet Communications Engine, is middleware for the practical programmer. A high-performance Internet communications platform, Ice includes a wealth of layered services and plug-ins. Ice means simplicity, speed, and power.
Ice is available under the terms of the GNU General Public License (GPL). Commercial licenses are available for customers who wish to use Ice with proprietary products. Please contact sales@zeroc.com for more information.
Ice is currently available for C++, Java, C#, Visual Basic, Python, and PHP, and is supported on various operating systems. Additional operating systems and languages will be supported in future releases.
Ice consists of the following packages:
Slice The Specification Language for Ice. Slice establishes a contract between clients and servers, and is also used to describe persistent data.
The Slice Compilers Tools to compile from Slice into target languages, such as C++ and Java, or to automatically generate documentation from Slice files.
Ice The Ice core library. Among many other features, the Ice core library manages all the communication tasks using a highly efficient protocol (including protocol compression and support for both TCP and UDP), provides a flexible thread pool for multi-threaded servers, and additional functionality that supports extreme scalability with potentially millions of Ice objects.
IceUtil A collection of utility functions, such as Unicode handling and thread programming. (C++ only.)
IceBox An application server specifically for Ice applications. IceBox can easily run and administer Ice services that are dynamically loaded as a DLL, shared library, or Java class.
IcePack A sophisticated server activation and deployment tool. With IcePack, the complex task of deploying applications in a heterogeneous computer network is dramatically simplified. Simply write a deployment descriptor in industry-standard XML, and IcePack handles the rest.
Freeze Freeze provides automatic persistence for Ice servants. With just a few lines of code, an application can incorporate a highly-scalable evictor that efficiently manages persistent objects.
FreezeScript It is common for persistent data types to change, especially in large software projects. In order to minimize the impact of these changes, FreezeScript provides inspection and migration tools for Freeze databases. The tools support an XML-based scripting capability that is both powerful and easy to use.
IceSSL A dynamic SSL transport plug-in for the Ice core. It provides authentication, encryption, and message integrity, using the industry-standard SSL protocol.
Glacier One of the most difficult challenges for object middleware systems is security and firewalls. Glacier, the firewall solution for Ice, greatly simplifies the deployment of secure applications. Glacier authenticates and filters client requests and allows callbacks to the client in a secure fashion. In combination with IceSSL, Glacier provides a powerful security solution that is both non-intrusive and easy to configure.
IceStorm A messaging service with support for federation. In contrast to most other messaging or event services, IceStorm supports typed events, meaning that broadcasting a message over a federation is as easy as invoking a method on an interface.
IcePatch A patching service for software distributions. Keeping software up-to-date is often a tedious task. IcePatch automates updating of individual files as well as complete directory hierarchies. Only files that have changed are downloaded to the client machine, using efficient compression algorithms.
Enhancements:
- Various additions, including redundant IceGrid registries.

Libtubo Interprocess Communication is a small and simple library that can run processes in the background and communicate via the stdout, stderr, and stdin file descriptors.
The functionality of libtubo is similar to the glib function g_spawn_async_with_pipes(), except that all pipe setup and monitoring is taken care of.
The calling function only has to provide the functions with which to process the input/output of the remote process.
The library first appeared in the year 2000 in the xfce3 desktop as part of the xfsamba application, and is now available for use for other developers.
Enhancements:
- Some control bugfixes.
- The version has been updated to the xffm scheme, as this package is now distributed with xffm.

Meldware Communication Suite is a platform independent groupware package consisting of:
Meldware Mail
Meldware Calendar
Meldware Webmail
Meldware Secure Administration System
Together the package provides support for thousands of users to concurrently send and receive email and schedule meetings. MCS uniquely allows you to store all messages and scheduling events in nearly any database and runs on nearly all popular software and hardware platforms.
Additionally, while the scheduling and calendaring services are able to be installed separately, the integrated featureset provides both a unique and powerful experience to both users and server-side Mail Based Applications and Collaboration Based Application Services.
The MCS platform provides security integration using LDAP sources including Microsoft Active Directory as well as flat-file and Database sources. Additionally, extensible security allows custom authentication/authorization sources.
Enhancements:
- IMAP is now stable with Mozilla Thunderbird and POP/SMTP are production ready.
- New Filestore code was implemented and many improvements were made in mailbox and storage code.

There is quite a bit of history on this item. One of the assignments in a computer graphics course at the University of Victoria was to rotate a number of Bezier curves around an axis and display the result in 3D using a single light source.

This was on Sun Sparcs using X. Since then the program has mutated to match my platform preference at a given time (DOS, Windows, Linux).

The latest mutation has been to SDL/OpenGL and the result runs happily on Linux and Windows. Screenshot junkies might find the following of interest:

dnshistory project provide a means for storing a history of DNS and Name changes for the IP Addresses extracted from web log files.
The major target being that multiple analyses of older log files do not require re-lookups of IP Address to FQDNs, and additionally maintain the accuracy of the lookup as it was then and not as it is now.
Main features:
- Do Lookups. The default mode. Given a web log file, dnshistory will perform DNS reverse lookups on each unique IP Address and store the results in a history database.
- Do Translations. Given a raw web log file, dnshistory will make use of a previously created history database and send to STDOUT the same web log but with addresses replaced by the Fully Qualified Domain Name as previously looked up.
- Do Recombining. Given two web log files, one raw and one previously translated (eg. by using dnstran): Create a history database from the values in these separate log files.
- Do Dump. Dump a given history database to STDOUT.
- Show History. Given one or more IP Addresses on the command line, display their history from the database.
Its quite possible that most users would only ever use the first two modes.
The lookups make use of threads for near maximum speed, and use the standard resolution libraries on a system. Thus hosts files, NIS, LDAP and other name resolution methods should work transparently. Unfortunately most other tools ignore local name resolution methods in favour of DNS lookups only.
It is strongly recommended that for massive raw lookups a DNS server is "nearby". Preferably not a forwarding server, or your upstream provider will not like you.
dnshistory can read .gz files. Any input sent via STDIN is currently assumed to not be gz encoded.
dnshistory assumes that the logs being sent are already sorted into oldest --> most_recent date/time order.
A Berkeley Database is used to store the history; as well as possibly reducing the memory footprint within a run.
dnshistory is released under the General Public License.
Enhancements:
- This is practically identical to 1.3-beta1.

CVS History is a Web application for searching the history of CVS actions. It parses the output of the CVS history command and imports it into a MySQL database for ease of manipulation by the PHP front-end.
Its advantage over other CVS history viewing applications is that it only needs anonymous CVS access to the repository.
Main features:
- Tested on Firefox and IE
- XHTML and CSS validated code
- RSS feed of the search query results
- Export the output of search query to other formats (e.g. CSV file)
- Searches can be bookmarked
- History entries can be linked to a ViewVC installation of the same repository

Browser-history is a small and efficient daemon that keeps your browser history, independent of the browser you use.
Browser-history came from the will to overcome a Netscape bug: there was no global history, and if you close a window, its whole history is lost. For people browsing lots of sites, having a possibility to track back where one has been before means that you dont have to put everything in your bookmarks file. If you are not sure if a site may be worth remebering, dont add it in your bookmarks. If you need it later, just browse your history files.
Later, it came to our minds that this also could be a valuable add-on to people writing experimental browsers, so they dont have to add this functionality to their browser itself, and to users able thus to track their web history regardless of the browser they used.
Browser-history is a small and efficient daemon. Real user services could be built on top of the log files it maintains for more possibilities (graphical representation, advanced search options, collective histories). It can be seen as a quick-and-dirty hack wrt to the general solution of using a personal proxy to provide this history and housekeeping facilities. For now, it is easy to use and it works very good.
And now that Netscape has a semi-decent history, browser-history is still valuable, as it is difficult to search in the netscape history, its file format is not defined, and entries expire after some time.
Enhancements:
- bugfix: since 2.6, internal links of default generated headers were false

Tie::HashHistory can track history of all changes to a tied hash.

SYNOPSIS

my $hh = tie %hash => Tie::HashHistory, PACKAGE, ARGS...;

@values = $hh->history(KEY);

Tie::HashHistory interposes itself between your program and another tied hash. Fetching and storing to the hash looks completely normal, but Tie::HashHistory is keeping a record of all the changes to the each key, and can Tie::HashHistory will give you a list of all the values the key has ever had, in chronological order.

The arguments to the tie call should be Tie::HashHistory, and then the arguments that you would have given to tie to tie the hash without the history feature. For example, suppose you wanted to store your hash data in an NDBM file named database. Normally, you would say:

tie %hash => NDBM_File, database, $flags, $mode;

to get this history feature, just add Tie::HashHistory before NDBM_File:

my $hh = tie %hash => Tie::HashHistory,
NDBM_File, database, $flags, $mode;

The data will still be stored in database, and it will still be an NDBM file. All the fetching and storing will look the same, but the change history of each key will be available.
The tie call will return an object; to find out the history of a key, use the history method on this object. It takes one argument, which is a key string. It will return a list of all the values that have ever been associated with the key, in chronological order, starting with the most recent. For example:

$hash{a} = first;
$hash{b} = second;
$hash{a} = third; # Overwrites old value

# Prints "third second" as you would expect
print "$hash{a} $hash{b}n";

@values = $hh->history(a);
# @values now contains (third, first)

@values = $hh->history(b);
# @values now contains (second)

At present, if called in scalar context, the history() method will return the number of items in the history. This behavior may change in future versions.

The underlying hash can be any tied hash class at all. To use a regular in-memory hash, use Tie::StdHash (distributed with Perl) as the underlying implementation:

use Tie::Hash; # *NOT Tie::StdHash*
my $hh = tie %hash => Tie::HashHistory, Tie::StdHash;

This is not as efficient as it could be because fetches and stores on %hash still go through two layers of tieing. I may fix this in a future release.