Hans Krutzer

I think this functionality is pretty critical. Personally I would want to have this for as many spans as possible, and definitely for active spans. So that means I would...

I see where you are coming from and the library can't handle every possible feature. However, I feel that it is within the Elixir way of doing things to support...

Yes, to support both client and server gRPC like https://github.com/elixir-grpc/grpc does an HTTP2 server would be needed (perhaps in the future it could work with [Bandit](https://github.com/mtrudel/bandit/issues/17). However, I'm only looking...

There is some documentation [here](https://developers.google.com/protocol-buffers/docs/proto?hl=en#services) and [here](https://developers.google.com/protocol-buffers/docs/reference/proto3-spec#service_definition). >wouldn't it be easier to use elixir-grpc? That library is unfortunately [no longer maintained])(https://github.com/elixir-grpc/grpc/graphs/contributors), and I would rather have client based on Mint....

One way of doing load balancing as mentioned on the linked document is using [xDS](https://github.com/grpc/grpc/blob/master/doc/grpc_xds_features.md), however, xDS has other features that might be useful as well but requires a lot...

I think Plug has https://hexdocs.pm/plug/Plug.ErrorHandler.html. Your option 2 seems best.

I'm not working on it in the foreseeable future so feel free to take it :)

Yes

I extracted the great work done in [Spear](https://github.com/NFIBrokerage/spear/) into a standalone gRPC client while this repo was inactive [here](https://github.com/hkrutzer/grpc_client). It might be of help.

I probably won't submit a PR anytime soon; streaming with that client can be done by sending messages, which I need for my own use case, and that doesn't look...