Improved client example with all request types

[DaniGuardiola]

No description provided.

[mattbennett]

Thanks for expanding these.

Can you perhaps move them to the block above (the nameko service client)? Otherwise it looks like the standalone client has special abilities, whereas it's really just a different usage.

Also I wonder whether using the @rpc decorator in that example is confusing, since it's so close to @grpc. It might be better to use @http or something obviously different.

[DaniGuardiola]

Also I wonder whether using the @rpc decorator in that example is confusing, since it's so close to @grpc. It might be better to use @http or something obviously different.

I would include examples for both, it makes it clearer.

[DaniGuardiola]

Examples structure now:

• Service client
  • @rpc method
    • unary-unary
    • unary-stream
  • @http method
    • stream-unary
• Standalone client
  • stream-stream

This way the four types of request-responses are covered, with both rpc and http method examples in the service client.

I'm thinking we could even include an example of gRPC service client, to show all options (and move one of the req-res types there, given that the rpc example has two).

[mattbennett]

@DaniGuardiola this is great, thanks. So per your final suggestion the example structure would be this?

• Service client
  • @rpc method
    • unary-unary
  • @grpc method
    • unary-stream
  • @http method
    • stream-unary
• Standalone client
  • stream-stream

I like it!