Affects Version/s: 0.20.0
Fix Version/s: None
I'd like to propose an improvement for consideration given my experience of working on
Currently the first call doubles up as a 'connection setup' trigger. I'd like to propose adding a new 'init' call which is always called by the clients for connection setup. The advantages are:
- We could fold in the getProtocolVersion call into the setup call, this ensures that the Server always checks for protocol versions, regardless of whether the (malicious?) client does an explicit call for getProtocolVersion or not.
- We could authorize the connection here.
- We could add to check to ensure that the Server instance actually implements the protocol used by the client to communicate, rather than fail on the first IPC call
The flip side being an extra round-trip.