Philip Zeyliger wrote:
Thinking out loud, the handshake could negotiate not just the schema for the protocol, but also the schema for the RPC metadata.
So we'd send a hash of the handshake's schema too? I think sending a magic number is equivalent and simpler.
Is the call-id value arbitrary bytes? We wouldn't break compatibility with what's currently published if the server was allowed to not set call-id if it was responding to things in order.
Yes, you're right. Requiring servers to copy the call-id to responses is an incompatible change. So is adding a magic number. But the spec currently does not yet define any transports, only request and response messages, which do not change. So we can consider this requirement and the addition of a magic number as a part of the specification of a TCP-based transport and label the existing implementation non-conforming.
Doug
