Skip to content

IPROTO_ID follow up #267

Closed
Closed
@DifferentialOrange

Description

@DifferentialOrange

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.

Metadata

Metadata

Labels

featureA new functionality

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions