ToDo-List & Ideas


The development of libTML started in 2002 as an internal project. Today Internet of Things (IoT) applications and Machine to Machine (M2M) messaging with new requirements are pushing the development of libTML. This roadmap covers only a few new features to be implemented in next versions.

1.1.5 language bindings

  1. Python Extension + class library
  2. Java (JNI) + class library
  3. Pascal + components for RAD Studio and Lazarus


  1. API to handle libTML connections. In Version 1.1 connections are handled almost transparently for the user. Information about the status of connections is not available neither is there an API to control connections except from setting some properties.
  2. Add encryption support based on the BEEP TLS profile and the Vortex TLS implementation.
  3. Add SASL support based on the BEEP SASL profile and the Vortex TLS implementation.


  1. Remove group/key structure from SIDEX data. This mechanism was pretty useful at the beginning of libTML. At that time no container types where available as variant types. With the improvement of containers like lists, dictionaries and tables the group/key structure became obsolete.
  2. Add optional data representations. The XML representation of SIDEX data structures is fast and reliable, but Internet of Things applications require a more compact format. UJO Data Object Notation will be added as an option to send the data in a binary format.
  3. Add optional JSON representation of SIDEX data.
  4. Add support of custom send and receive functions for connections to use libTML on any transport protocol providing a full duplex data stream.