Grpc-go: support generate asynchronous interface for golang implementation
the C and Java implementation will generate asynchronous interface, but golang implementation not, is there a plan ? or some reason ?
NeoCN
All 5 comments
There's generally no reason to have async APIs in Go. It's trivial enough to start a new goroutine when you have need for that.
dsymonds
on 14 Jul 2015
when use c client code with async method to invoke golang grpc server, there will be a problem, because there is no async server interface, unless to modify the generated code. @dsymonds
NeoCN
on 14 Jul 2015
You're not making any sense. What problem are you observing in your Go program?
dsymonds
on 14 Jul 2015
"async" is not a property of the method. It is simply the way the method is invoked from the point of view of the invoker. Synchronous and asynchronous versions of the same method send functionally equivalent data on the wire, which is consistent with either form of the method on the server side. There is no problem with sending an RPC using the async interface with a C client and handling it with a synchronous go server.
murgatroid99
on 14 Jul 2015
get it, thanks @murgatroid99. I will give it a try.
NeoCN
on 14 Jul 2015
Related issues
ericchiang
路
3Comments
dfawley
路
3Comments
kushp
路
4Comments
arcana261
路
3Comments
ahmetb
路
4Comments
Most helpful comment
"async" is not a property of the method. It is simply the way the method is invoked from the point of view of the invoker. Synchronous and asynchronous versions of the same method send functionally equivalent data on the wire, which is consistent with either form of the method on the server side. There is no problem with sending an RPC using the async interface with a C client and handling it with a synchronous go server.