Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe failure responses #26

Open
jwise-mfg opened this issue Dec 16, 2024 · 2 comments
Open

Describe failure responses #26

jwise-mfg opened this issue Dec 16, 2024 · 2 comments
Labels
review next Request for the Working Group to review at the next opportunity

Comments

@jwise-mfg
Copy link
Member

Splitting out from #3

If I read many elements and one fails, (ex. bad ID) what is the behavior?

These interfaces should define failure causes, what is returned on a read failure, bad elementID, etc

@randy-armstrong
Copy link

The OPC UA approach is to provide StatusCodes at each level.

i.e. reading X values means a StatusCode array in the response with length = X.

@jwise-mfg jwise-mfg added the enhancement New feature or request label Jan 14, 2025
@aronsemle
Copy link

I think you should get a status for each elementid you read, as Randy points out.

As an implementer, the tricky part is if you read something that's complex (ex. OPC UA branch). OPC UA is going to return status codes for each node in the branch. So the implementor has to decide, do I allow a "partial" result where some underlying things failed but it's still useful to return some data, or do is it all or nothing. The same applies if the thing your are reading has a data from different sources (ex. OPC and SQL).

From the perspective of the standard, do we think the client cares? Should we have some Good/Partial status or some way for the client to be aware of this? I think probably not, and we could add it later if there is a need.

@jwise-mfg jwise-mfg added review next Request for the Working Group to review at the next opportunity and removed enhancement New feature or request labels Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
review next Request for the Working Group to review at the next opportunity
Projects
None yet
Development

No branches or pull requests

3 participants