On 5/12/19, Nick Couchman <[email protected]> wrote: >> >> My error. ChainedTunnel does fallback to HTTP; my testing was done >> incorrectly. >> So I'll reduce my question to: >> 1. Is there a way to report this on the browser? >> > > Kind of depends on what you mean by "report" - it does get "reported" to > the browser and captured by the ChainedTunnel implementation, which turns > around and tries the next tunnel. I think if you wanted to do something > else with it, like log it in the browser or display an error, you'd need to > implement your own version of the ChainedTunnel that handles those failures > as you require. You could use the existing HTTP and WebSocket tunnels > defined in the Tunnel.js file, but don't use ChainedTunnel and, instead, > customize your own implementation that suits your needs. > > What is it that you mean by "report" and what are you trying to accomplish?
Yes, I'd like to log to the browser. However, if this requires implementing a new ChainedTunnel, I don't think the tradeoff is worth it. I'll keep the errors logged on server side only.
