Separate events’ emitting nodes from their SourceNodes
!! Warning, API-breaking changes! When closely reading the spec, events are emitted by one node, and refer to their SourceNode in an attribute — the SourceNode can and often will be different from the emitting node. Until now, python-opcua assumed these two to be identical. This commit tries to straighten this situation. To that end, we introduce new parameters in the eventgenerator, Event-class and all children thereof. The EventGenerator will now try to honor emitting nodes given to it, but still handle and add SourceNodes. The InternalSubscription finally serializing and emitting the event is adapted to this new behavior.
Showing
This diff is collapsed.
Please register or sign in to comment