You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my exploration of the EdgeX Foundry IoT platform and it's ecosystems, I've encountered a notable design choice regarding device-opc-ua library connection properties such as Security Policy, Security Mode, and Server Cert Path being placed within the configuration.xml file. Initially, I found this decision somewhat perplexing. My rationale was that these properties might vary between different OPC servers, leading me to consider whether configuring these properties through protocol-specific settings could offer greater flexibility.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In my exploration of the EdgeX Foundry IoT platform and it's ecosystems, I've encountered a notable design choice regarding device-opc-ua library connection properties such as Security Policy, Security Mode, and Server Cert Path being placed within the configuration.xml file. Initially, I found this decision somewhat perplexing. My rationale was that these properties might vary between different OPC servers, leading me to consider whether configuring these properties through protocol-specific settings could offer greater flexibility.
Beta Was this translation helpful? Give feedback.
All reactions