JonasH-munters commented on PR #2251: URL: https://github.com/apache/plc4x/pull/2251#issuecomment-3281485250
Thank you for the response and I definitely think I might be one of the confused ones so any clarifications that can be done on the PLC4X API level as a result of this PR will be great I think :D Just gotta figure out the best clarifications to do! What you say makes sense for cyclic subscriptions so maybe removing the `addCyclicTag` and `addCyclicTagAddress` methods with a `consumer` parameter from the `DefualtPlcSubscriptionRequest.Builder` class would make sense? Or some other way of reducing user confusion compared to the current state where the consumers are just ignored. But I was under the impression that for the `PlcSubscriptionType.CHANGE_OF_STATE` ones that I'm using the plc event only contains the ones that actually had their values change. When I debug with a breakpoint in the `OpcuaSubscriptionHandle` class I can see that the `DataChangeNotification` object that I receive most of the time contains only 18 values of 74 tags I subscribed to in my test case. Is that not how OPC UA change of state subscriptions should work? If not, maybe it could be relevant to support anyway since it seems at least the server I'm using (Kepware) behaves that way? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
