Closed gregmedd closed 4 months ago
CallOptions is never sent as a uProtocol message. Instead of being a layer-0 message, it was used as a layer-2 client API.
It is being removed in favor of allowing language-specific API libraries to define the most appropriate function signatures for the language.
Addresses issue #132
CallOptions is never sent as a uProtocol message. Instead of being a layer-0 message, it was used as a layer-2 client API.
It is being removed in favor of allowing language-specific API libraries to define the most appropriate function signatures for the language.
Addresses issue #132