protocol: removed globals allow race-free object removal

Without this clarification, clients cannot reliably remove objects
created transitively from a bound global.

Signed-off-by: Julian Orth <ju.orth@gmail.com>
This commit is contained in:
Julian Orth 2022-05-09 14:05:16 +02:00
parent 2dcc35af81
commit f59194de17

View file

@ -165,9 +165,13 @@
the global using the bind request, the client should now
destroy that object.
The object remains valid and requests to the object will be
ignored until the client destroys it, to avoid races between
the global going away and a client sending a request to it.
Until the client destroys the object, the compositor will
ignore other requests to the object except that, for any
request that adds new objects to the compositor state,
the compositor will continue to add the new objects to
its state. These new objects transitively follow the same
rules.
</description>
<arg name="name" type="uint" summary="numeric name of the global object"/>
</event>