X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fipc;h=bcf8df1aa4abe5ba1c86fced66f689aba2fd05b4;hb=484854d52fc44d0aeec25986c659b8262706dace;hp=e44ffd7ce20f2c38230bef3e137e02f73a22ea0e;hpb=6339427f017e1265a022e6537e16a8b4a921e52f;p=i3%2Fi3

diff --git a/docs/ipc b/docs/ipc
index e44ffd7c..bcf8df1a 100644
--- a/docs/ipc
+++ b/docs/ipc
@@ -693,6 +693,14 @@ program does not want to cope which such kinds of race conditions (an
 event based library may not have a problem here), I suggest you create a
 separate connection to receive events.
 
+If an event message needs to be sent and the socket is not writeable (write
+returns EAGAIN, happens when the socket doesn't have enough buffer space for
+writing new data) then i3 uses a queue system to store outgoing messages for
+each client. This is combined with a timer: if the message queue for a client is
+not empty and no data where successfully written in the past 10 seconds, the
+connection is killed. Practically, this means that your client should try to
+always read events from the socket to avoid having its connection closed.
+
 === Subscribing to events
 
 By sending a message of type SUBSCRIBE with a JSON-encoded array as payload