flatbuffers/grpc/examples
lu-wang-g fd4ff23da0
Keep methods with struct name and switch them to default (#6879)
* Keep methods with struct name and switch them to default

This PR can help fix the following two issues:
1): A set of simplified API (without struct name) was added in
https://github.com/google/flatbuffers/pull/6336. It causes name
conflict when merging all generated python file into a single one
(the primary usage senario in Google).
2): Flatbuffers 2.0 generates absolute import path, which may cause
name space conflicts. See more details in
https://github.com/google/flatbuffers/issues/5840.

The solution for both is to generate the merged Python code, similar
C++. The merged code will not contain the simplied API, but only the
method with struct name. For issue (1), it will mimic the exactly
usage pattern for Google internal. For issue (2), users can generate
the merged flatbuffer code, without worrying about the imports.

The above idea will be implemented in the following steps:
Step 1 (this PR): revert changes in https://github.com/google/flatbuffers/pull/6336
that set the simplified API as default. Remove statements that the
original API will be deprecated, and reset the original API as default.
Step 2 (the following PR): create a flag to generate the merged code.
The Simplified API will be removed from the merged code, otherwise it
will cause name conflict.

* Update the generated sample code

* Update the generated example code

* Reverst the changes of GetRootAs

* Update examples from grpc/example/generate.sh
2021-11-04 15:12:25 -07:00
..
go Updates go lang support to allow other languages to communicate with it (#6653) 2021-05-20 11:32:56 -07:00
python/greeter Keep methods with struct name and switch them to default (#6879) 2021-11-04 15:12:25 -07:00
swift/Greeter Adds JSON encoding to swift (#6874) 2021-10-07 23:22:22 +02:00
ts/greeter Adds JSON encoding to swift (#6874) 2021-10-07 23:22:22 +02:00
README.md Working on a python example plus fixing python grpc code (#6456) 2021-02-25 14:38:12 -08:00
generate.sh Adds JSON encoding to swift (#6874) 2021-10-07 23:22:22 +02:00
greeter.fbs [Go] Working on a go example plus fixing go grpc code (#6448) 2021-02-19 12:47:59 +03:00

README.md

Languages known issues

Python

  • Assert the type required in your server/client since python is able to receive Bytes array or utf8 strings.
def SayHello(self, request, context):
    # request might be a byte array or a utf8 string

    r = HelloRequest.HelloRequest().GetRootAs(request, 0)
    reply = "Unknown"
    if r.Name():
        reply = r.Name()
    # Issues might happen if type checking isnt present.
    # thus encoding it as a `reply.decode('UTF-8')`
    return build_reply("welcome " + reply.decode('UTF-8'))

This can be prevented by making sure all the requests coming to/from python are Bytes array

def say_hello(stub, builder):
    hello_request = bytes(builder.Output())
    reply = stub.SayHello(hello_request)
    r = HelloReply.HelloReply.GetRootAs(reply)
    print(r.Message())

Go

  • Always requires the content-type of the payload to be set to application/grpc+flatbuffers

example: .SayHello(ctx, b, grpc.CallContentSubtype("flatbuffers"))