You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Twirp canonical implementation supports both server and client interceptors. This allows us to do similar things for both clients and servers, such as emit specific metrics based on type of request. In the Ruby stack, this facility exists only for the server side. Are there any plans to introduce client interceptors as well?
As a side note, what twirp-ruby calls service hook is actually server interceptor in the canonical lingo. Any reason for this naming choice?
The text was updated successfully, but these errors were encountered:
The Twirp canonical implementation supports both server and client interceptors. This allows us to do similar things for both clients and servers, such as emit specific metrics based on type of request. In the Ruby stack, this facility exists only for the server side. Are there any plans to introduce client interceptors as well?
As a side note, what twirp-ruby calls service hook is actually server interceptor in the canonical lingo. Any reason for this naming choice?
The text was updated successfully, but these errors were encountered: