Skip to content

why tarpc? #42

@rbtcollins

Description

@rbtcollins

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions