Yea, that currently seems to be the best way, and creating a JSON codec is
pretty simple too.
However, my concern is that by doing so, there is no more code generation.
I've only followed the tutorials, but it seems the grpc code generation
generates a lot of things such as interfaces for implementing the grpc
server, types and all the stuff to work with streams which is a huge
productivity boon.
Another problem is that Server.RegisterService() takes an
interface{}: https://godoc.org/google.golang.org/grpc#Server.RegisterService
without the code generation, I am not sure what ss should look like.
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/d1436363-6bac-4928-bbb2-63e41dd472a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
