Is there any risk to adding a custom payload to a message type that is
explicitly documented as having an empty response body?
Thanks -- Joel.
On 8/27/2025 2:59 PM, Abe Ratnofsky wrote:
Bret - I agree with your interpretation of the spec. “Currently only X is
supported” is not a prescriptive statement about the protocol, as I had
initially read it.
We should encourage client implementations to log client warnings and expose
the custom payload for the READY response after protocol negotiation - are you
on board with that? If so, we should mention this in the spec and update
cassandra-java-driver.
