The current Twirp maintainers aren't interested in adding timeouts to the wire protocol (see twitchtv/twirp#329). They've done a remarkably good job keeping the protocol tiny, so I'm not surprised.
Currently, reRPC servers respect the Grpc-Timeout header, even when the content-type indicates that the client is using the Twirp protocol. This seems relatively harmless, but perhaps we should stick to the minimal spec and drop this support?
The current Twirp maintainers aren't interested in adding timeouts to the wire protocol (see twitchtv/twirp#329). They've done a remarkably good job keeping the protocol tiny, so I'm not surprised.
Currently, reRPC servers respect the
Grpc-Timeout
header, even when the content-type indicates that the client is using the Twirp protocol. This seems relatively harmless, but perhaps we should stick to the minimal spec and drop this support?