From 2c93bd6e8982e2d7b1c33b9f221e36348552d215 Mon Sep 17 00:00:00 2001
From: Tor Lillqvist <tml@collabora.com>
Date: Thu, 29 Sep 2016 14:40:56 +0300
Subject: [PATCH] Document the 'pong' message

Should the 'pong' have a colon to match other server->client messages?
Consistency is a virtue.
---
 loolwsd/protocol.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/loolwsd/protocol.txt b/loolwsd/protocol.txt
index c50744367..c22babf72 100644
--- a/loolwsd/protocol.txt
+++ b/loolwsd/protocol.txt
@@ -246,6 +246,10 @@ nextmessage: size=<byteSize>
     must be handled by clients that cannot (like those using Poco
     1.6.0.
 
+pong
+
+    sent in reply to a 'ping' message
+
 status: type=<typeName> parts=<numberOfParts> current=<currentPartNumber> width=<width> height=<height> viewid=<viewId> [partNames]
 
     <typeName> is 'text, 'spreadsheet', 'presentation', 'drawing' or 'other. Others are numbers.