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
Hi ! (followed your link in Linkedin to github, but since the website linked in the github org metadata is a 404, I can't ask these naive questions outside of the bug tracker. Sorry!).
So the first one is - why tarpc? I mean, it seems nice, but it seems vulnerable to cross-language portability issues (such as having to redefine the protocol in every language, or use a transport orientated schema like openapi/swagger rather than the much more precise protobuf. google/tarpc#161 is closed but not particularly satisfactorily.
I had a good look around and couldn't find any motivating decision for this. I would have expected tower-rs+tonic or similar to be the default choice.
The text was updated successfully, but these errors were encountered:
Hi ! (followed your link in Linkedin to github, but since the website linked in the github org metadata is a 404, I can't ask these naive questions outside of the bug tracker. Sorry!).
So the first one is - why tarpc? I mean, it seems nice, but it seems vulnerable to cross-language portability issues (such as having to redefine the protocol in every language, or use a transport orientated schema like openapi/swagger rather than the much more precise protobuf. google/tarpc#161 is closed but not particularly satisfactorily.
I had a good look around and couldn't find any motivating decision for this. I would have expected tower-rs+tonic or similar to be the default choice.
The text was updated successfully, but these errors were encountered: