M&M FDT 1.2.1 Online Specification
 4.10.3 Dual Interfaces


Interfaces and Methods   -   Schemas   -   FDT Specification   -   Quicklinks   -   Abbreviations

Up to FDT Specification

4.1 Overview of the FDT interfaces
4.2 FDT Objects
4.2.1 FDT Object Model
4.2.2 DTM State Machine
4.10 General Concepts
4.10.1 Task Related FDT Interfaces
4.10.2 Return Values of Interface Methods
4.10.3 Dual Interfaces
4.10.4 Unicode
4.10.5 Asynchronous vs. Synchronous Behavior
4.10.6 ProgIds
4.10.7 Slave Redundancy
4.10.8 Field Bus Scanning and DTM Assignment

4.10.3 Dual Interfaces

All interfaces defined within the FDT Specification are implemented as dual interfaces. This decision was made to support C++, Visual Basic, Java and other COM compliant development languages. The functionality of an object is implemented in separate task oriented interfaces, so that only the default interface is accessible via the dispatch interface. This prevents marshaling of the extra interfaces to dispatch-only clients, but the extra interfaces can be made available for a dispatch only-client via a wrapper that holds the other interfaces as properties or merges all methods to a single interface.
Due to the better performance, the developer should use the custom interface. However, in general the dispatch interface can be accepted, because the marshalling time of most of the FDT methods can be neglected compared with the runtime of each method.



© 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.