Good point! :)
I'll give that a go.
On Wednesday, January 11, 2017 at 8:54:13 AM UTC+11, Carl Mastrangelo wrote:
>
> Personally I would generate the code once and then just modify it to work
> with my custom codec. Having the autogenerated code is nice, but since
> you don't need most of it, I think you'll find you pay the costs without
> any of the benefits.
>
>
> On Tuesday, January 10, 2017 at 1:50:58 PM UTC-8, Francis Chuang wrote:
>>
>> 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/f1479b2e-c7f9-480f-a4e5-0f42680a8356%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
