XHAM - TODO
 

Home
SF Home
Docs
Download
Developers
FAQ
To-do List
Credits
Thanks
 

As this project is at its very beginning state, I therefore have so many outstanding tasks to do. I am also looking for more resources such as developers, technical writers, and test engineers who could help me finishing the following tasks:

Task Description Target Date
2003-001 Failsafe Architecture Design Document (ADD) - High Level Design of System Failsafe, Application Failsafe, and Deadlock Failsafe. The document shall describe how can each module be used and interconnected in each particular type of failsafe. Jan-2004
2003-002 XHAM Modules Specification Document (MSD) - The document shall describe the specification of each particular module in XHAM project such as what is parameters to invoke the module, return value, global environment, pre & post conditions, etc. Jan-2004
2003-003 XHAM Modules Block Test Specification (BTS) - Considering each module as a black box, how can we test it? To write this document, you may need to refer to XHAM Modules MSD. Mar-2004
2003-004 Change appmon's configuration format - Present configuration is not user friendly yet. We prefer Samba format (which is very easy to understand) to clumsy XML one. Oct-2003
2003-005 Heartbeat-UDP - Currently, heartbeat-ping is stable but in some networking environment "icmp-echo" is not allowed through Firewall or, in some case, the server itself rejects ICMP Echo. We therefore need alternative. Heartbeat-UDP will send UDP echo to monitor availability of a particular system or application. There must be heartbeat-udp's APIs which can be used "inside" application server and client. For the time being, we focus at C/C++ APIs only. However, Java APIs is in our pipeline as well but there is no timeframe yet. Mar-2004
2003-006 Heartbeat-TCP - Currently, heartbeat-ping is stable but in some networking environment "icmp-echo" is not allowed through Firewall or, in some case, the server itself rejects ICMP Echo. We therefore need alternative. Heartbeat-TCP will send TCP echo to monitor availability of a particular system or application. There must be heartbeat-tdp's APIs which can be used "inside" application server and client. For the time being, we focus at C/C++ APIs only. However, Java APIs is in our pipeline as well but there is no timeframe yet. Apr-2004
2003-008 Deadlock Monitoring - This module can only be bundled inside the application. The rough idea is application needs to register deadlock-monitoring client with deadlock-monitoring server before requesting for any mutex semaphore. Deadlock-monitoring client will continually send heartbeat to its server while processing instruction in the risky area. If there is any deadlock happened in the application after registration, deadlock-monitoring server will receive any heartbeat. Then it will restart that particular application accordingly. To maintain integrity, when it is about to release all reserved mutex, it shall cancel deadlock-monitoring registration first. Nov-2004

If you are interesting to contribute to our project, you will be more than welcome. For more detail, please contact xeruz@users.sourceforge.net.

Xeruz

January 16, 2003




Questions? Comments? Suggestions? Last updated:
$Date: 2003/08/15 05:42:59 $