-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathAsync Methods Actor Release Notes.txt
More file actions
18 lines (18 loc) · 2.98 KB
/
Async Methods Actor Release Notes.txt
File metadata and controls
18 lines (18 loc) · 2.98 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Async Methods Actor Release Notes
v1.0.0
- Removed unused Async Message property write methods
- Added a "Async Message Settings" to be used by the LS AF Message Maker to create send methods for the concrete Async Messages
- Removed dependencies on OpenG Error and Variant libraries. This allows exporting code to previous versions of LabVIEW
- The Example now leverages on the Async messages created by the LSI AF Message Maker v2.0
- In order to be able to create Async messages by means of the LSI AF Message Maker v2.0, a master copy of the Example was created that links to the Async Methods Actors VIPM package. Herein we create Async messages by the LSI AF Message Maker v2.0, since the latter links to the Async Methods Actors VIPM. Once this is done the Example is copied to the git version folder the VIPM is uninstalled and the Example is relinked to the git source
v0.3.0
- 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 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 (Issue # 3)
- Added the functionality of reporting the standard error output of the Async Method to the calling actor (Issue #4)
- Added the ability to access the error in the Async Method standard output form within the "Completion Notification Msg" message. A further abstract subclass called "Compl Notif with Error Msg" was introduced whose Do.vi method merges the standard error output of the Async Method executed and that defines a new dynamic dispatch method to be overridden, called "Actor Core.vi" to implement a caller Actor method call (Issue #1)
v0.2.0
- Added an infrastructure that enables the caller of Async Message to be informed about the completion of "Call and Collect" Async methods
- Now every executed Async Message is identified by a GUID
- 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
- Completed and updated README.md documentation and methods/properties docstrings
v0.1.0
- Initial public release