TMI uses an application protocol based on XML. Even though XML provides a degree of extensibility and flexibility in the protocol design, the drawbacks of applying XML as the data format standard for the communication protocol consist of the following:
XML parsing requires more system resources compared to other data formats such as CGI name-value pair and binary structure (the program leaves a large footprint on your server or device).
The agent footprint required to transfer information is much larger in XML compared with other data formats.
Data processing performance is slower due to the larger data footprint.
Packet transmissions take longer and the transmission rate is less than other data formats.
MCP's data format is designed to resolve these issues. MCP's data format is a BLOB (binary) stream with each item composed of name ID, type, length, and value. This BLOB format has the following advantages:
Smaller data transfer size compared to XML: Each data type requires only a limited number of bytes to store the information. These data types are integer, unsigned integer, Boolean, and floating point.
Faster parsing speed: With a fixed binary format, each data item can be easily parsed one by one. Compared to XML, the performance is several times faster.
Improved design flexibility: Design flexibility has also been considered since each item is composed of name ID, type, length, and value. There will be no strict item order and compliment items can be present in the communication protocol only if needed.
In addition to applying binary stream format for data transmission, more than one type of data can be packed in a connection, with or without compression. With this type of data transfer strategy, network bandwidth can be preserved and improved scalability is also created.