I'm confused about how you can call a method from a Thrift 0.14.1 netstd
client to a Java server. All the netstd clients have appended "Async" to every
method name. The Java server doesn't have those methods defined.
For example, if I define a method call "foo" in my service definition in the
.thrift file, it creates a method "fooAsync" in the netstd client and "foo" on
the Java service.
Looking at the t_netstd_generator.cc file, it doesn't seem like there is any
way to avoid appending the "Async" suffix. I have tried manually changing the
generated code from:
await oprot.WriteMessageBeginAsync(new TMessage("fooASync", ...
to
await oprot.WriteMessageBeginAsync(new TMessage("foo", ...
and it works.
So I suppose I could write a shell script on our build server to fixup the
generated .cs files at build time, but that seems cumbersome.
What am I missing?
