Person Issuse

[1511563371]

Hi，Bro. Is the current framework running in the production environment?

[Tradias]

At 3YOURMIND we have been using asio-grpc in production without any hiccups for 4 years. Someone who opened an issue here in the past said that they are using asio-grpc for a motion capture application, another said they plan on using it on automotive-grade Linux to back a flutter app. There are also several open source projects that use asio-grpc like: https://github.com/Ultimaker/CuraEngine, https://github.com/meta-soul/MetaSpore, https://github.com/erigontech/silkworm

[1511563371]

Hi，Bro!
I still have three questions to ask:
Question 1: Does the current framework support the flatbuffers protocol?
Question 2: Can the current framework use the quic protocol as its transport layer?
Question 3: How can I use the grpc framework or related plugins to use the current framework?

[Tradias]

1. I haven't tested it in a while but it should work. You should follow the instruction from flatbuffers to generate the necessary files from your .proto files: https://github.com/google/flatbuffers/tree/master/grpc
2. Asio-grpc does no implement any transport protocol. It is merely a thin layer on top of gRPC which uses HTTP2 internally
3. There is no question of how, you must use at least the grpc_cpp_plugin from gRPC to generate C++ sources from .proto files to use with asio-grpc.

[1511563371]

Hello, bro！
Is the default IO processing framework of the asio-grpc framework io_uring based on the linux kernel or a user-space framework?

[Tradias]

Asio-grpc does not implement any IO processing framework. It utilizes gRPC which uses epoll on Linux. GRPC is working on a so called EventEngine which will allow asio-grpc to create an implementation based on asio::io_context and io_context supports io_uring.

[1511563371]

Hi, bro.
The current framework is as a cmake package.

cmake -B build -DCMAKE_INSTALL_PREFIX=/desired/installation/directory .
cmake --build build --target install

using stdexec:

find_package(asio-grpc CONFIG REQUIRED)
find_package(stdexec)
target_link_libraries(your_app PUBLIC asio-grpc::asio-grpc-stdexec STDEXEC::stdexec

Should the IO model in the framework be replaced with the IO model in stdexec ?

[Tradias]

The IO framework would still be provided by gRPC. Asio-grpc provides wrappers for grpc::CompletionQueue that satisfy the stdexec::scheduler concept for example. Once gRPC completes the implementation oj their EventEngine, exec::io_uring_context could be used to power gRPC's IO.

[1511563371]

Hi,Bro!
current,I wanna us asio-grpc only with
Currently, I only want to use asio-grpc and bo-boost asio instead of grpc-c++. Is this idea okay?

[Tradias]

I am not sure I understand. Asio-grpc makes no effort to be usable without gRPC. Some headers like https://github.com/Tradias/asio-grpc/blob/master/src/agrpc/waiter.hpp can be used without it though.