Adl2

Description: This Sample application demonstrates the usage of ADL2 APIs in the application that contains multiple uncoordinated ADL transactions. ADL2 APIs have been added to ADL to allow creation of the applications that contain multiple clients that call ADL2 APIs in uncoordinated manner without risking destroying each other’s context. You can use legacy ADL and newer ADL2 APIs in the same application. The only limitation is that no more than one client that uses ADL APIs can exist at any given time in the same process. There is no limit to number of clients that use ADL2 APIs. This sample demonstrates how to author application that contains multiple ADL2 transactions and single legacy ADL transaction.

Supported OS: Windows

Init and Destroy: Initialize the library before using it and destroy it after the usage. Refer to InitADL() for initialization and clean-up is done inside main function only.

Adapter Status:

• “GetAdapterActiveStatus”: Retrieves active status of given adapter with “ADL2_Adapter_Active_Get”. Implements the retrieval as isolated ADL2 transaction. Note that the function can be nested inside another ADL2 transaction without interfering with it. In real application it would be much more efficient to share the same context with the parent transaction by passing the context handle in the function argument list.

Adapter Information:

• “PrintAdapterInfo”: Execution of multiple nested ADL2 transactions that are executed on the same thread. Uncoordinated ADL2 transactions can be also executed on separate thread.
• Invoking additional nested ADL2 based transaction on the same thread to demonstrate that multiple ADL2 transactions can be executed at the same time inside the process without interfering. Not the most efficient way to work with ADL. In real application it would be much more efficient to re-use context of parent transaction by passing it to “GetAdapterActiveStatus”.

Sample Path: Sample\Adl2