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

Deprecate /single PATCH Interface #174

Open
Mantls opened this issue Mar 5, 2024 · 0 comments
Open

Deprecate /single PATCH Interface #174

Mantls opened this issue Mar 5, 2024 · 0 comments

Comments

@Mantls
Copy link

Mantls commented Mar 5, 2024

By allowing for incomplete Requests to be made via HTTP Patch using the /single Interface a more or less undocumented state-machine is created.

Apart from that request validation and general data handling becomes much simpler and convenient if implementations can expect complete requests. With less small pitfalls and potential mismatches between implementations interoperability should ultimately be improved as well.

In practice i have yet to see a controller that patches incomplete data to a sender or receiver.

In contrast i've seen many default to only using the /bulk interface in combination with polling of the respective /active resources. Nodes of course don't have this luxury since they have to implement both.

/bulk pretty much handles everything /single does so why not deprecate it simplifying and narrowing down the API in the process.

This is something for a v1.2 of course.

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

1 participant