Version 1.1.2 of BitEvolution

Release Notes: The BitEvolution client and server were updated to load the default configuration files from the working directory if it was not specified on the command line. The Updater class was updated to select the first available port from the range of 5002-5999 if one is not specified. The UpdateAnalyzer was updated to use the MD5 file comparison when determining if a file has been updated instead of the date and time stamp on the file.

Other releases

  •  21 Jun 2006 23:29

Release Notes: A new custom update frame has been added that can be used to give BitEvolution the Windows update look and feel. You can override the default update frame by adding a configuration parameter to the client properties file. In addition, custom update frames can be easily written and plugged into BitEvolution. Documentation about configuring and managing multiple update tracks was added. The Updater class was updated to allow users to specify a range of ports to select from when performing communication. A threading issue in the SocketMonitor class was fixed.

  •  22 Mar 2006 02:24

Release Notes: The Server was updated to allow duplicate location elements to allow content to be retrieved from multiple locations. Various documentation typos and errors were fixed.

  •  11 Mar 2006 23:04

Release Notes: The UpdateFrame interface was added to allow developers to write custom windows to change the look and feel of the BitEvolution Client. An introduction to writing custom update frames was added. This tutorial takes you through implementing and deploying a simple update frame from start to finish. The client installation documentation was updated. Various JavaDoc typos and errors were fixed.

  •  08 Mar 2006 01:40

Release Notes: The BitEvolution client and server were updated to load the default configuration files from the working directory if it was not specified on the command line. The Updater class was updated to select the first available port from the range of 5002-5999 if one is not specified. The UpdateAnalyzer was updated to use the MD5 file comparison when determining if a file has been updated instead of the date and time stamp on the file.

  •  04 Mar 2006 07:27

Release Notes: This release adds an introduction to writing custom update tasks. This tutorial takes you through implementing and deploying a simple update task from start to finish. The release also fixes a null pointer exception in the Client and Server classes which occurred when specifying an unqualified configuration file on the commandline.

Screenshot

Project Spotlight

Aspose.Cells for .NET

A .NET component for spreadsheet reporting without using Microsoft Excel.

Screenshot

Project Spotlight

CloverETL Designer

A visual data transformation designer for the CloverETL framework.