[11:19] <dimitern> hey guys, anyone around?
[11:20] <dimitern> I have a question how do you handle client api websocket connections going down
[11:21] <dimitern> frankban, teknic: maybe you can help? ^^
[11:22] <dimitern> oops teknico ^^
[11:23] <teknico> dimitern: maybe :-) go on
[11:24] <dimitern> teknico: so there's a way to ping a websocket connection and verify it's still alive
[11:24] <dimitern> teknico: are you using this with the gui?
[11:26] <teknico> dimitern: possibly, let me have a look
[11:29] <teknico> dimitern: we use Y.ReconnectingWebSocket
[11:29] <frankban> dimitern: IIRC we use a reconnecting websocket, reconnecting when the onclose message arrives. The websocket connection should have a readyState attr set to 1 if the connection is open
[11:30] <dimitern> frankban, teknico: So this I presume uses some form of pinging internally? Where's the code?
[11:31] <teknico> dimitern: http://bazaar.launchpad.net/~juju-gui/juju-gui/trunk/view/head:/app/assets/javascripts/reconnecting-websocket.js
[11:32] <teknico> dimitern: invoked from http://bazaar.launchpad.net/~juju-gui/juju-gui/trunk/view/head:/app/store/env/base.js#L172
[11:33] <dimitern> teknico: istm you're reconnecting when the connection is closed, but not actively monitoring whether it's stil alive
[11:33] <teknico> dimitern: yes, that's my understanding too
[11:33] <dimitern> teknico: ok, thanks for checking
[11:33] <teknico> dimitern: yw
[13:38] <frankban> dimitern: could you please review https://codereview.appspot.com/9641044 ?