Instead of emitting a wserror event (WebSocket? whichServer?), emit a
standard error event. Inspect the provided Error object if it's important
to know which condition caused the error.
Add a fail-safe timeout in case the WebSocket doesn't emit a wserror
event, and we also haven't heard from the server in a couple of minutes.
This can happen in cases where a malfunctioning or misconfigured
application-aware proxy/firewall sits between the client and server.
Adjust example to reflect event name change
Document the "error" event.