Nikolai Lubiagov

I found, i can just use: `LIBS += -lgrpc++` instance of: ``` CONFIG += link_pkgconfig PKGCONFIG += grpc++ ``` And seems it is not have conflict...

pkgconfig way also dependent of grpc and protobuf library: ``` prefix=/usr exec_prefix=${prefix} includedir=${prefix}/include libdir=${exec_prefix}/lib Name: gRPC++ Description: C++ wrapper for gRPC Version: 1.30.2 Cflags: -I${includedir} Requires: grpc protobuf Libs: -L${libdir}...

Oops ... really got into trouble with this now.... :-( in many things i plan to use... As far as I understand, bi-directional stream does not accept any data immediately....

you men option `QT_PROTOBUF_NATIVE_GRPC_CHANNEL` ? or what exactly? In principle, it is obvious that we will need to make changes to the project code. At a minimum, the current API...

I while not recompile sources... And not try use Native Channel but If i right understand https://github.com/semlanik/qtprotobuf/blob/c6d7977a544f004f26215f01d207aae599fb6139/src/grpc/qgrpcchannel.cpp#L90 Hard to understand code for me, but seems, it create separate thread for...

I try to play.... Sync method normal working if i use `grpc::ByteBuffer` as argument/response; But async method, not: ``` ::grpc::ClientAsyncReader* reader=grpc::internal::ClientAsyncReaderFactory::Create(ch.get(),&queue,method,&clientContext, request, true, tag); ``` `Read` not fill buffer at...

My mistake, normal work with grpc::ByteBuffer async method. I just didn't take into account the fact that the buffer is filled not in the Read method, but in the Next...

If QtNetwork is not suitable for this, we can use both the native implementation and other HTTP2 libraries. Hacking with private classes I would be afraid to use because of...

https://github.com/lubagov/qtprotobuf/commit/b4ade2efb6814c004466fa05c4f3dccc8017a5a3 something terrible seems to have done. But the methods are asynchronous now. Although I very much doubt the correctness and thread safety. (Really think batter call method in thread...

I am currently trying to add bidirection subscriptions. Just a question why there is no `emit` in front of many signals in the code?