xdg-shell: Document responsibilities regarding ping events

Document that a compositor is free to ping in any way it wants, but a
client must always respond to any xdg_shell object it created.

Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
This commit is contained in:
Jonas Ådahl
2015-05-05 15:35:16 +08:00
committed by Bryce Harrington
parent 5b77199cc1
commit 7a9bb0ea00
+3
View File
@@ -123,6 +123,9 @@
alive. It's unspecified what will happen if the client doesn't alive. It's unspecified what will happen if the client doesn't
respond to the ping request, or in what timeframe. Clients should respond to the ping request, or in what timeframe. Clients should
try to respond in a reasonable amount of time. try to respond in a reasonable amount of time.
A compositor is free to ping in any way it wants, but a client must
always respond to any xdg_shell object it created.
</description> </description>
<arg name="serial" type="uint" summary="pass this to the pong request"/> <arg name="serial" type="uint" summary="pass this to the pong request"/>
</event> </event>