Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use existing RPC mechanisms instead of inventing new ones #5

Open
juberti opened this issue Jul 23, 2019 · 3 comments
Open

Use existing RPC mechanisms instead of inventing new ones #5

juberti opened this issue Jul 23, 2019 · 3 comments

Comments

@juberti
Copy link
Collaborator

juberti commented Jul 23, 2019 •
edited
Loading

Trunk creation, call creation, and signaling byways are basically HTTP RPCs, and there are many existing frameworks for doing such things, e.g., https://grpc.io, https://thrift.apache.org/, etc. I'd suggest that we not reinvent this particular wheel.
@fluffy
Copy link
Member

fluffy commented Jul 24, 2019

Agree and gRPC has worked well for me on other stuff. I would likely go that way over thrift.

@suhasHere
Copy link

suhasHere commented Jul 24, 2019 •
edited
Loading

+1 on gRPC .. I played with it and works neat

@juberti
Copy link
Collaborator Author

juberti commented Jul 24, 2019

I think the IETF would definitely benefit from having a real RPC-over-HTTP mechanism defined (i.e. other than REST)

jdrosen added a commit that referenced this issue Feb 6, 2020
@jdrosen
Update draft-rosenbergjennings-dispatch-ript.md
cfdb333 
Cullen #5: remove peak-concurrent calls as part of TG construct
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fluffy @suhasHere @juberti