-
Notifications
You must be signed in to change notification settings - Fork 62
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Improved cmake tests configuration * Added option to remove occurrence in unary call * Added option for occurrence in unary call * Added without occurrence option for streaming calls * Restructured the code * Made occurrence changes to streaming vi templates * Updated route_guide example * Updated route_guide example * Fixed route_guide clients * Updated helloworld example * Changed activeclientcalls to unordered_map * Removed wait from cleanUpProc * Added feature toggle for occurrence * Improved occurrence wrapper * Added feature toggle docs * Bumped vipb version to v1.2.1.1
- Loading branch information
Showing
17 changed files
with
281 additions
and
185 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Introducing Feature Toggles | ||
|
||
Starting from release v1.2.0.1 we have added support for feature toggles. This allows you to enable or disable certain features in the application without the need to redeploy the application. | ||
|
||
## How to use feature toggles | ||
|
||
Feature toggles are managed through the `feature_config.ini` file (located next to _labview_grpc_server_ library). You can find the `data` section in the file. Here is an example of how to use feature toggles: | ||
|
||
```ini | ||
[data] | ||
EfficientMessageCopy = TRUE | ||
useOccurrence = TRUE | ||
``` | ||
|
||
In the example above, the `EfficientMessageCopy` and `useOccurrence` features are enabled by default. If you want to disable a feature, you can set the value to `FALSE`. | ||
|
||
### More about the flags | ||
|
||
1. `EfficientMessageCopy` - This feature is used to enable or disable the efficient message copy feature. When enabled, the client will use efficient message copy to have throughput. When disabled, the client will use the default message copy. | ||
|
||
2. `useOccurrence` - This feature is used to enable or disable the occurrence feature. When enabled, the client will use occurrence to manage synchroniation between LabVIEW execution threads. When disabled, the client will use not use LabVIEW occurrences. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file modified
BIN
+212 Bytes
(100%)
labview source/gRPC lv Support/Client API/Client Complete Client Streaming Call.vim
Binary file not shown.
Binary file modified
BIN
+228 Bytes
(100%)
labview source/gRPC lv Support/Client API/Client Read From Stream.vim
Binary file not shown.
Binary file modified
BIN
-84 Bytes
(100%)
labview source/gRPC lv Support/Client API/Client Unary Call.vim
Binary file not shown.
Binary file modified
BIN
+684 Bytes
(100%)
labview source/gRPC lv Support/Server API/Server/Get Server DLL Path.vi
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.