Passing connection errors to the onerror() handler? about simple-websocket-server

[eidheim]

Thank you again. I replaced the exception throws with onerror calls.

[eidheim]

I have to think some more on this, though my initial thought is that the on-methods should be triggered only after a websocket connection is established. I think it should somehow be possible retry opening the connection if these exceptions are triggered.

[eidheim]

Or are you running several clients on one io_service.run()?

edit: if so, you are probably right.

[classix-do]

Exactly.
I have a bigger application, which starts a Simple-Web-Server to provide dynamic content and opens a long running websocket client connection for data exchange and I wanted them both to share one io_service. I also decoupled the Thread, running the io_service.run() so that it doesn't know anything about the web server or websocket client, which are using the same io_service.

If onerror should only handle errors, which occur during an open connection, then maybe you could make client.start() accept a callback function, which only gets called if an error occurred during connect().