From 425ff5e7d687f162321d1cde1aed426678abba22 Mon Sep 17 00:00:00 2001 From: Pekka Paalanen Date: Mon, 4 Nov 2024 16:56:18 +0200 Subject: [PATCH] color: make invalid id illegal This started from https://gitlab.freedesktop.org/swick/wayland-protocols/-/merge_requests/90 where it was desireable for a compositor to send invalid image description ids because it does not track and de-duplicate image description records. Concensus decided the opposite: the id number must be valid. The ability to skip get_information request was seen valuable, and the effort to implement id allocation was deemed not too high. It is also to the majority taste to deliver image descriptions with valid id. Signed-off-by: Pekka Paalanen --- staging/color-management/color-management-v1.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/staging/color-management/color-management-v1.xml b/staging/color-management/color-management-v1.xml index bdfb8e5..a882c9a 100644 --- a/staging/color-management/color-management-v1.xml +++ b/staging/color-management/color-management-v1.xml @@ -1367,7 +1367,8 @@ Image description id number is not a protocol object id. Zero is reserved as an invalid id number. It shall not be possible for a client to refer to an image description by its id number in protocol. The id - numbers might not be portable between Wayland connections. + numbers might not be portable between Wayland connections. A compositor + shall not send an invalid id number. This identity allows clients to de-duplicate image description records and avoid get_information request if they already have the image