IPROTO_ID follow up
DifferentialOrange opened this issue · 1 comments
DifferentialOrange commented
While implementing IPROTO_ID in go-tarantool (see tarantool/go-tarantool#226), we had discovered that some things could be done better, like
- storing server and client version and features separately,
- requiring protocol version/features on connect to fast fail if server doesn't support then.
We need to catch on the Go implementation.
DifferentialOrange commented
It seems that _check_features is not triggerred on reconnect.