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.

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

feature request / idea: generating JSONRPC2 client proxies from GRPC #272

Closed
joeblew99 opened this issue Nov 28, 2016 · 1 comment
Closed

Comments

@joeblew99
Copy link

joeblew99 commented Nov 28, 2016

I noticed that this code gens a swagger document from which you can use the swagger project to generate client proxy code. All great but i am thinking that code generating JSONRPC2 from GRPC is a much tighter match.

Essentially my clients are coded in Dart and dart has great support for JSONRPC2.
There is not GRPC support yet, and it looks a long way off because of web browser issues. Long story.

So, from my basic checking, it looks like GRPC --> JSONRPC2 is pretty simple translation.
Here is a great example of 2 in pure GRPC & JSONRPC2:
https://blog.gopheracademy.com/advent-2015/etcd-distributed-key-value-store-with-grpc-http2/

It shows how GRPC and JSONRPC2 is so similar, and so its reasonable to conclude that Client code that is generated will also be similar.

Curious what other people think..

@joeblew99 joeblew99 changed the title feature request / question: jsonrpc2 feature request / idea: generating JSONRPC2 client stubs from GRPC Nov 28, 2016
@joeblew99 joeblew99 changed the title feature request / idea: generating JSONRPC2 client stubs from GRPC feature request / idea: generating JSONRPC2 client proxies from GRPC Nov 28, 2016
@achew22
Copy link
Collaborator

achew22 commented Jan 4, 2017

@joeblew99 Thanks for your interest in the project. Unfortunately it doesn't look like anyone has the time/energy combined with the need to implement this. The two solutions (gRPC and JSONRPC2) are similar enough that, for my use case, I'm happy to just use gRPC. If you're interested in taking that task on, I would personally be interested in seeing your implementation. This project may not be the right place for it. Feel free to add me to a PR in a new repo if you decide to take this task on.

I'm also going to close the issue to help keep things tidy but I hope to see you around in the future.

@achew22 achew22 closed this as completed Jan 4, 2017
@tamalsaha tamalsaha mentioned this issue Mar 30, 2017
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants