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

How should clients fail on encountering invalid list members? #126

Open
johannhof opened this issue Jan 5, 2023 · 1 comment
Open

How should clients fail on encountering invalid list members? #126

johannhof opened this issue Jan 5, 2023 · 1 comment

Comments

@johannhof
Copy link
Member

This is a discussion I had previously with @cfredric: How should clients behave when a part of the list is invalid (e.g. no primary domain on a set)? Should they fail "gracefully" by only dropping the invalid part of the list (e.g. the affected set) or, given that the server should deliver correct information in all cases (and otherwise be informed about a malformed list, reject the entire list altogether?

We should come to an agreement and document that in the spec.

@dmarti
Copy link

dmarti commented Jan 5, 2023

I would prefer to have the client reject the entire list. This would mean more people would be likely to detect and report the problem. A graceful failure could result in a partly broken state persisting longer, which would be more likely to overlap with other things being partly broken and increase the total troubleshooting effort for web developers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants