Don't consume MetaIoHandler until all error handling is done about jsonrpc

[tomusdrw]

Binding to port number 0 should cover your use case, you can get assigned port from Server (I think it's not implemented for WS transport, because that feature is missing upstream).
Which transport do you use?

[faern]

Oh. Stupid me. How did I not think about that... Thanks

However, I do use websocket at the moment so it won't help me right away. Maybe I can help patch it to support this though? So this feature is missing from the ws crate? And after adding it there it should likely work for this ws server implementation?

[tomusdrw]

Correct. I have a PR pending that lays some ground for this, but don't have enough time to finish it: housleyjk/ws-rs#133
Feel free to add this feature there.

[faern]

I tried it out just now and binding to port 0 does bind to a random port number, as it should. The problem is that server.addr() still reports port 0, and not the port it was actually assigned. I see, will see if I find time to help fix that.

[faern]

@tomusdrw Your PR seems a bit outdated with regard to master. I'll see if I can fix it directly on upstream and then maybe you can adapt your code. Would be nice if jsonrpc-ws-server could use ws directly from crates.io. Anything else stopping that?

[tomusdrw]

To use ws from crates.io was the exact purpose of that PR, the critical thing is that we need arbitrary responses to handshake.

[faern]

This will be solved by #146