You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: