PubSub

[ziopio]

A basic PubSub communication has been implemented but the way for it to read and write in the address space is hacky and should be disciplined before merging.

Things to do before merging this PR:

• Make the PubSub entities use a configurable address space
• Mirror in some way the PubSub entities in the server informational model
• Allow server methods to act on the informational model to read/write the PubSub state

[peerst]

Why is this not merged yet?

[ziopio]

IIRC, this PR implements the protocol but does not add anything to the informational model. It is just the protocol part of Opcua PubSub without all the integration required to use it between OPCUA endpoints.

We left this here waiting to implement the full integration with the informational model and to make it useable by the user through OPCUA abstraction. Am I right @sylane ?

Unfortunatly we never came back to it.

[sylane]

IIRC we had to stopped working on that, so there is some integration and testing work left.