BaseWebSocketBehavior currently calls Wicket.WebSocket.createDefaultConnection() on DOM ready. I would like to be able to delay connection creation and trigger it myself.
Desktop users of our application tend to open quite a number of tabs from search result pages and other lists and Wicket creates a new websocket connection for all tabs opened in the background.
I implemented a solution that uses the Page Visibility API to open and close websocket connections when a page becomes visible or hidden. Since I currently cannot disable the default connection, I'm closing the connection immediately:
This works, but most browsers log an error like this:
A configuration option to disable automatic connection creation would solve this.