Kevin Herron
Kevin Herron
So, I feel like I managed to talk myself in a full circle yesterday and arrived right back at what you originally posted. You seem to have a clear grasp...
The first approach you outlined resonates with me the most, but that's probably because it's the most similar to how our application uses Milo (minus any kind of redundancy support)....
The spec doesn't enforce that constraint on client handles, but any sane client implementation should be using unique client handles per item, at least within the context of a single...
FWIW, after looking at this and discussing with you, my take on this is that client redundancy is under-spec'd and under-supported in the current revisions of the OPC UA spec...
I think you can start prototyping this approach with minimal changes in Milo at first. Everything discussed so far can happen outside the SDK, but there will be some changes...
No this functionality isn't implemented right now.
No, probably not soon.
Unfortunately there's not much more info I could tell you. The Bad_CertificateUseNotAllowed StatusCode comes from the server and does not include more information. If you can share your certificate(s) I...
I will take that into consideration but it's not immediately obvious to make that more clear. FWIW, a UaServiceFaultException can only be generated when a ServiceFault is received from the...
Yeah that would be another case that would need to be determined by looking the stack trace. I had once considered using a different Exception type for errors generated client-side...