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 an use case from our server implementation it is required to add an own network layer, which should not be visible to any common tcp-based client. Is this possible today?
My current approach is to extend the struct UA_ConnectionConfig with the element UA_Boolean internalUseOnly. But to hide this network layer/endpoint to the common clients I must extend the function Service_GetEndpoints:
In an use case from our server implementation it is required to add an own network layer, which should not be visible to any common tcp-based client. Is this possible today?
My current approach is to extend the struct UA_ConnectionConfig with the element UA_Boolean internalUseOnly. But to hide this network layer/endpoint to the common clients I must extend the function Service_GetEndpoints:
Any opinions?
Br
Martin
The text was updated successfully, but these errors were encountered: