For protocol buffers, the file needs to be shared out of band. The proto file is used to generate actual running code for each client which is what the client needs to communicate in the first place.
To give a technically correct answer, Server reflection is possible to dynamically discover what the remote endpoint knows. It can be used to get all the protos the server is willing to speak. It is not turned on by default though. On Wednesday, March 22, 2017 at 9:44:20 PM UTC-7, Judes HONORE wrote: > > > I would like to understand how I can request from a gRPC service from a > outside client. > > According to this example on github ( > https://github.com/grpc/grpc/tree/master/examples/node/dynamic_codegen), > the client need a proto file dependency. > How can a distant client (outside local scope) should require this proto > file ? > > Does node.js have a module like grpc-gateway to add REST > retro-compatibility for web client access ? > > Can you give me an example projet that implement those problems ? > > Thx for all your future responses > > Regards, Judes HONORE. > -- 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/9c23a552-8766-4ec7-a1ef-be61509c1729%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
