4 ms·
hi - i checked the logs. I presume it's the corporate network I'm in blocking the websocket stuff WebSocket connection to 'wss://precursorapp.com/chsk?tab-id=
by planetjones 11y ago
hi - i checked the logs. I presume it's the corporate network I'm in blocking the websocket stuff
WebSocket connection to 'wss://precursorapp.com/chsk?tab-id=883d69ff-1095-4eed-bf63-83d786d55db1&client-id=f71e3c9b-fd70-4710-8502-ada0c73f4760' failed: Error during WebSocket handshake: Unexpected response code: 200
Maybe you could add some better error handling into the GUI ?
- dwwoelfel 11y agoOh no! It's supposed to fall back to long-polling if it can't set up a WebSocket connection. Thanks for letting us know.
- Trufa 11y agoAny news? I still can't use it.
- dwwoelfel 11y agoSorry, I have the ajax fallback mostly working. Sharing cursors doesn't work, but syncing chat and changes to the canvas does. I'm still trying to find a reliable way to catch the error that prevents the connection upgrade. Right now, the library I'm using thinks that it should just keep retrying the websocket connection. We're already maintaining our own fork of the library, but it's a tedious process to make and test changes.
- jkarneges 11y agoA good practice is to do it the other way around: start with long-polling and switch over to WebSockets only once it's confirmed to work. Don't know which library you're using but I know some do this.