Page History

...

clientName and clientVersion could be sent in every request alongside to the clientId in the header. While this would be fairly simple to implement once KIP-482 is implemented, it would make adding more metadata we believe it is not suitable if we want to collect more information in the future hard and would wast few bytes in every request for something which does not change within a session. It also makes the error handling weird as a request could be rejected due to its headers. Another issue is that we haven't found a way to evolve the header of the ApiVersionsRequest/Response to support tagged fields.

Put clientName and clientVersion in the RequestHeader but provide it only once

clientName and clientVersion could be added to the RequestHeader but sent only in the first request to save bytes in the subsequent requests. Concretely, it means sending The best would be to have it in the ApiVersionsRequest in order 's header but it is impossible (see previous point). It would be weird to have the info as soon as possible in the broker. Why not putting it in the ApiVersionsRequest directly? Moreover, it would make the implementation of a client ambiguousinformation in random requests and could make clients inconsistent.

Add a new request to communicate the client metadata to the broker

...