Hooray! Some comments:
"Granularity per channel, per server level". Can you please clarify? Does this mean that a server cannot have 2 or services, some async and others sync? If so, what about pre-packaged services like healthcheck? It will also be a hurdle for easy and gradual adoption of the async API into servers and organizations. Will running functions in executors be fully supported? It is a common pattern to run sync tasks in executors on the asyncio event loop using https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.run_in_executor. The executors can be process or thread pools, will both be supported out of the box? grpc.aio.Call functions return asyncio.Future, but grpc.ServerContext.send_initial_metadata returns a Task object. Could you please elaborate on the rationale here? grpc.aio.channel_ready_future not returning a future, but a coroutine. This can be surprising. asyncio Exceptions ( will they be mapped to gRPC Errors where possible)? While the RFC states that the RPCError exceptions will be the same, it does not speak to how https://docs.python.org/3/library/asyncio-exceptions.html are mapped, if at all. There is a comparison between the current gRPC API and the proposed, but it might be valuable to do a similar take from the asyncio perspective -- what are the functions/facilities that will be unavailable with the gRPC async API and how can the similar actions be performed. Eg: asyncio.* functions such as gather,shield, wait_for, wait, etc - It would be very nice if the gRFC could include the full API, given that this is a new package, and list functions that will be exported ( ie: added to __all__) Thanks! On Mon, Jul 22, 2019 at 1:49 PM 'Lidi Zheng' via grpc.io < [email protected]> wrote: > Hi gRPC users, > > This proposal is about adding a new set of Async IO native API to gRPC > Python, which solves concurrency issues and performance issues for gRPC > Python. > The new API will be isolated with current API, so the migration can happen > gradually. > > gRFC: > https://github.com/lidizheng/proposal/blob/grpc-python-async-api/L58-python-async-api.md > PR for the gRFC: https://github.com/grpc/proposal/pull/155 > > Comments and suggestions are welcomed! > > Lidi Zheng > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/92d5e57f-332a-4e48-bdb2-ccc4d515a5bf%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/92d5e57f-332a-4e48-bdb2-ccc4d515a5bf%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAFEPE9SLaayUMkcnp8kAxWwoBXYZBuQvT7VT_pDJ71xskMwhmA%40mail.gmail.com.
