plugins: cannot close websocket connections or set a message timeout

[alessiodf]

It is currently not possible for a plugin to close an open websocket connection, as the websocket's close function is not exposed via the sandbox.

In addition it would be extremely useful to trigger an event if no data is received on the socket after x seconds since the last message, in order to detect dead sockets. This would be much better done plugin-side if #1446 were implemented but in the absence of that facility, it would need to be added to the websocket code by clearing a timer when the message event is fired and then restarting the timer again.

[ghost]

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

[ghost]

This issue has been closed. If you wish to re-open it please provide additional information.