| |||
Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations | |||
| Up to FDT Specification 3.1 Abstract 3.2 Introduction 3.3 Component Interoperability 3.4 FDT Type Library 3.5 DTM and Device Versions 3.6 Persistence 3.7 Nested Communication 3.7.1 Data Exchange 3.7.2 Communication Channel Upgrade 3.7.3 Scenarios 3.7.4 OnAddChild 3.8 Implementation Hints 3.8.1 Interfaces 3.8.2 Persistence | 3.7.1 Data ExchangeAn XML document exchanged via IFdtCommunication and IFdtCommunicationEvents can contain version dependent attributes and elements. Unlike attributes of a newer version, which can be defined and handled as optional, new elements in a higher version would not be recognized by the parent component of an older version and can produce unpredictable behaviour in such a component. Therefore a DTM can only use communication documents according to the FDT version of its parent component. This version information of the parent component must be provided within the IFdtCommunicationEvents2::OnConnectResponse2(). A DTM can then use only communication documents compatible to this FDT version. | ||
© by M&M Software GmbH, parts of this website taken from FDT Interface Specification Version 1.2.1, © by FDT Group, AISBL. This website is published for support of M&M products as granted in license conditions, chapter 2.1. Last updated 2015-02-05 15:17 Email: FDT Technical Support Line. | |||