Log In
Home
07/10/2018
Offline
Hello,
i’m currently working on an Aggregation-Server. I want to aggregate serveral servers of the same type, so i have n-times the same namespaces to aggregate. Is there any specification, how to aggregate serveral identic namespaces? I saw the concept of putting the serveruri as a prefix to the namespace-uri. Is that a valid approach or do i get any conflicts relating to companion specifications.
05/30/2017
Offline
application-uri+namespace-uri is unique if the application-uri are properly assigned by the admins.
a generic aggregator has to deal with misconfigured servers.
07/10/2018
Offline
Yes the application-uri is unique. But when i aggregate two identical servers, i have two sets of the same namespace array.
Is it conform to change the original namepace-uri to application-uri+namespace-uri?
05/30/2017
Offline
You need to determine whether the namespace is a static ‘type model’ or a dynamic ‘instance model’.
If it is a static model you cannot change the URI and you have merge the namespaces from multiple servers (usually not an issue because the type model is from a third party NodeSet such as DI).
If it is an instance model you can change the URI.
The NamespaceMetadataType tells you whether a namespace is static if it has static node ids defined.
Note that the NamespaceMetadataType allows a namespace to be both an instance model and a type model. You will need to keep the URI for the NodeIds in the static range and create new URIs for NodeIds outside the static range. However, in many cases you will never see nodes outside of the static range so you should not incur overhead assuming they might appear (i.e. the dynamic URI does not get added unless a NodeId outside the static range was encountered).
1 Guest(s)
Usage Policy