- From: Drasko DRASKOVIC <drasko.draskovic@gmail.com>
- Date: Thu, 29 Oct 2015 12:06:12 +0100
- To: "Nilsson, Claes1" <Claes1.Nilsson@sonymobile.com>
- Cc: "public-wot-ig@w3.org" <public-wot-ig@w3.org>
On Thu, Oct 29, 2015 at 11:50 AM, Drasko DRASKOVIC <drasko.draskovic@gmail.com> wrote: > Hi Nilsson, > > On Thu, Oct 29, 2015 at 3:12 AM, Nilsson, Claes1 > <Claes1.Nilsson@sonymobile.com> wrote: >> Referring to previous maiol discussion on this topic I attach a few slides that I may show at our ongoing Sapporo TPAC meeting, e.g. at the TF-AP breal out session. > > Thanks for these slides. > > I have one question regarding CoAP (and WS) which I do not understand > very well -for this scenario: > 1) client (IoT device) initiates connection towards he cloud (WS or CoAP) > 2) once the connection is established it stays open > > But how long does it stays open? Until the server handles the request? > Until some TCP timeout? Unitl some server internal WebSocket timeout? >From what I read here: http://www.tcpipguide.com/free/t_TCPConnectionManagementandProblemHandlingtheConnec-3.htm, TCP connection should never close, and keepalives on this level are not even necessary. On the application layer, if the WebsocketServer can keep connection ON without closing it, then there is no need for keepalives from device (nor from server). Connection will be idle, but open. Or am I missing something? BR, Drasko
Received on Thursday, 29 October 2015 11:06:39 UTC