Skip to content

Commit 1a246fc

Browse files
committed
VI Server Refnums Lifetime
Introduced a "VI Refnum Lifetime" enumeration which can take values "Destroy on Exit", " Destroy on Actor Exit ", and “Destroy on Application Exit” (Feature #3). This enumeration dictates the lifetime strategy adopted for the VI Server Refnum of the Async Method. In the first case the "Async Methods Actor" destroys the reference as soon as the Async Method exits, in the second case the VI Refnums will be destroyed once the “Async Method Actor” exits, while in the last case, VI Refnums are never destroyed. “Destroy on Exit” is the default option when un-wired. The motivation for this setting is related to the required lifetimes of the refnums (e.g. notifier’s references) created within the Async Method. This lifetime is the same as the VI Refnum lifetime, hence if we want they outlive the execution of the Async Method we have to set it to either “Destroy on Actor Exit” or “Destroy on Application Exit”. This option applies only to Async Methods called with the “Call and Collect” option.
1 parent e9b95c1 commit 1a246fc

31 files changed

Lines changed: 165 additions & 60 deletions

Async Methods Actor Example/Async Methods Actor Example Messages/VI Refnum Lifetime Test Msg/VI Refnum Lifetime Test Msg.lvclass

Lines changed: 49 additions & 0 deletions
Large diffs are not rendered by default.

Async Methods Actor Example/Async Methods Actor Example.lvlib

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@
1111
<Item Name="Async Messages" Type="Folder">
1212
<Item Name="Alternative Long Execution Method Msg.lvclass" Type="LVClass" URL="../Async Methods Actor Example Messages/Alternative Long Exec Meth Msg/Alternative Long Execution Method Msg.lvclass"/>
1313
<Item Name="Long Execution Method Msg.lvclass" Type="LVClass" URL="../Async Methods Actor Example Messages/Long Execution Method Msg/Long Execution Method Msg.lvclass"/>
14+
<Item Name="VI Refnum Lifetime Test Msg.lvclass" Type="LVClass" URL="../Async Methods Actor Example Messages/VI Refnum Lifetime Test Msg/VI Refnum Lifetime Test Msg.lvclass"/>
1415
</Item>
1516
<Item Name="Ack Completion Long Exec Meth Msg.lvclass" Type="LVClass" URL="../Async Methods Actor Example Messages/Ack Completion Long Exec Meth Msg/Ack Completion Long Exec Meth Msg.lvclass"/>
1617
<Item Name="Cancel Long Exec MetH Msg.lvclass" Type="LVClass" URL="../Async Methods Actor Example Messages/Cancel Long Execution Methods Msg/Cancel Long Exec MetH Msg.lvclass"/>
Binary file not shown.

Async Methods Actor Example/Async Methods Actor Example/Async Methods Actor Example.lvclass

Lines changed: 32 additions & 21 deletions
Large diffs are not rendered by default.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
Async Methods Actor Release Notes
2-
2+
v0.3.0
3+
- Introduced a "VI Refnum Lifetime" enumeration which can take values "Destroy on Exit", " Destroy on Actor Exit ", and “Destroy on Application Exit”. This enumeration dictates the lifetime strategy adopted for the VI Server Refnum of the Async Method. In the first case the "Async Methods Actor" destroys the reference as soon as the Async Method exits, in the second case the VI Refnums will be destroyed once the “Async Method Actor” exits, while in the last case, VI Refnums are never destroyed. “Destroy on Exit” is the default option when unwired. The motivation for this setting is related to the required lifetimes of the refnums (e.g. notifier’s references) created within the Async Method. This lifetime is the same as the VI Refnum lifetime, hence if we want they outlive the execution of the Async Method we have to set it to either “Destroy on Actor Exit” or “Destroy on Application Exit”. This option applies only to Async Methods called with the “Call and Collect” option.
34
v0.2.0
45
- Added an infrastructure that enables the caller of Async Message to be informed about the completion of "Call and Collect" Async methods
56
- Now every executed Async Message is identified by a GUID
67
- It is now possible to choose a communication method (notifiers or event) by which a subscriber can be informed about currently running "Call and Collect" Async methods and launched running "Call and Forget" Async methods. The communication is off by default
78
- Completed and updated README.md documentation and methods/properties docstrings
89
v0.1.0
9-
- Initial public release
10+
- Initial public release

0 commit comments

Comments
 (0)