summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Ådahl <jadahl@gmail.com>2015-05-05 15:35:16 +0800
committerBryce Harrington <bryce@osg.samsung.com>2015-05-21 19:05:41 -0700
commit7a9bb0ea004ce2a813e3beda3de9caec07a4407d (patch)
treeeb5a91fa76d19139fcd98a652bc1ba5a4efb43a7
parent5b77199cc1ad9d971d9ef51c9f21ef6149942193 (diff)
downloadweston-7a9bb0ea004ce2a813e3beda3de9caec07a4407d.tar.gz
weston-7a9bb0ea004ce2a813e3beda3de9caec07a4407d.tar.bz2
weston-7a9bb0ea004ce2a813e3beda3de9caec07a4407d.zip
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>
-rw-r--r--protocol/xdg-shell.xml3
1 files changed, 3 insertions, 0 deletions
diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml
index 06a6cfd6..72570363 100644
--- a/protocol/xdg-shell.xml
+++ b/protocol/xdg-shell.xml
@@ -123,6 +123,9 @@
alive. It's unspecified what will happen if the client doesn't
respond to the ping request, or in what timeframe. Clients should
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>
<arg name="serial" type="uint" summary="pass this to the pong request"/>
</event>