กก

HISTORY OF CHANGES

                                                                       made to the TMO Toolkit since v4.1.8

กก

v4.2.1
01/15/2007

  • Time representations in TMO are updated.
  • RMP protocols are updated.  (For  advanced users only)
  • RMMC IP broadcast is supported.

v4.1.9
04/13/2006

Most of the changes of this version are the improvements/optimizations on TMOSM itself.  Only a few APIs are added  for advances users.

  • Improved the heap management module to avoid deadlocks.
  • Added the support for TMO destruction.  (For  advanced users only)
  • Added the RMMC Broker mechanism.
  • Modularized TMOSM to support multiple plug-in communication subsystems support. (For  advanced users only)
  • Added the support for cluster Environments including the MPI plug-in comm. subsystem. (For  advanced users only)
  • Added multiple clock synchronization strategies, include broadcast-based clock sync. mechanism in LAN/cluster environments.

v4.1.8d
05/23/2005

  • Revised the TMO Support Library user manual
  • All APIs involving an Official Release Time (ORT) now support the definition of the ORT parameter in 'MicroSec' format in addition to the 'tms' format

v4.1.8c
05/17/2005

  • Fixed a bug would produce in some cases a "Not enough memory available" error message when a RMMC is created
  • Fixed a bug that would cause "Wrong Event Msg Type" error messages when more than one TMO and more than one RMMC are used on the same node
  • Updated the middleware interface for user scheduler plug-ins

v4.1.8b
05/05/2005

  • Added optional error report warning services
  • Modified the content of the config.ini file and the corresponding config assistant tool
  • Fixed a bug occurring on  machines having multiple network cards / IP addresses (binding error)
  • Fixed minor bug in the TMOSM initialization sequence
  • Added the user scheduler plug-in feature. This feature allows users to create and use their own Method Execution Thread (MET) scheduler. This powerful new feature has intentionally been ignored in the TMOSL manual in order to restrict its usage. Only collaborative researchers who can provide a "significant" TMO program will receive the information and assistance they need.

v4.1.8
04/09/2005

Initial version