From 25716261e0c9609a014cc76d5c1462d77c30897b Mon Sep 17 00:00:00 2001 From: kansi Date: Wed, 25 Oct 2017 13:47:02 +0530 Subject: [PATCH] Updated keep-alive section --- .../source/events/websocket-event-stream-api.rst | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/server/source/events/websocket-event-stream-api.rst b/docs/server/source/events/websocket-event-stream-api.rst index 0000107b..7eb3f3f5 100644 --- a/docs/server/source/events/websocket-event-stream-api.rst +++ b/docs/server/source/events/websocket-event-stream-api.rst @@ -40,11 +40,14 @@ response contains a ``streams`` property: Connection Keep-Alive --------------------- -The Event Stream API initially does not provide any mechanisms for connection -keep-alive other than enabling TCP keepalive on each open WebSocket connection. -In the future, we may add additional functionality to handle ping/pong frames -or payloads designed for keep-alive. +The Event Stream API supports Ping/Pong frames as descibed in +`RFC 6455 `_. +.. note:: + + It might not be possible to send PING/PONG frames via web browsers because + of non availability of Javascript API on different browsers to achieve the + same. Streams -------