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.

Sign up for GitHub

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

Jump to bottom

handle invalid values at servers #32

Open

i-n-g-o opened this issue Dec 13, 2023 · 0 comments

Member

i-n-g-o commented Dec 13, 2023 •

edited

Loading

A server must not rely on values sent from clients to be within the bounds a parameter specifies. It needs to pre-evaluate a value-update and either:

reject the update
- A rejected value must not be sent to other clients and the current value needs to be sent back to the client.
confine the value within its bounds (clip, scale, do-nothing, ...)
- A corrected value is to be sent back to the sending client.

This shall not be part of the protocol specification but server implementers need to consider this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment