QGrpcHttp2Channel Class

Detailed Description

Uses QGrpcChannelOptions and QGrpcCallOptions to control the HTTP/2 communication with the server.

Use QGrpcChannelOptions to set the SSL configuration, application-specific HTTP/2 headers, and connection timeouts.

QGrpcCallOptions control channel parameters for the specific unary call or gRPC stream.

QGrpcHttp2Channel uses QGrpcChannelOptions to select the serialization format for the protobuf messages. The serialization format can be set either using the content-type metadata or by setting the QGrpcChannelOptions::serializationFormat directly.

Using the following example you can create a QGrpcHttp2Channel with the JSON serialization format using the content-type metadata:

auto channelJson = std::make_shared<
QGrpcHttp2Channel>(QGrpcChannelOptions{ QUrl("http://localhost:50051", QUrl::StrictMode) }
                       .withMetadata({ { "content-type"_ba,
                                         "application/grpc+json"_ba } }));

Also you can use own serializer and custom content-type as following:

class DummySerializer : public QAbstractProtobufSerializer
{
    ...
};
auto channel = std::make_shared<
    QGrpcHttp2Channel>(QGrpcChannelOptions{ QUrl("http://localhost:50051", QUrl::StrictMode) }
                       .withSerializationFormat(QGrpcSerializationFormat{ "dummy",
                                                  std::make_shared<DummySerializer>() }));

QGrpcHttp2Channel will use the DummySerializer to serialize and deserialize protobuf message and use the content-type: application/grpc+dummy header when sending HTTP/2 requests to server.

QGrpcChannelOptions::serializationFormat has higher priority and if the content-type metadata suffix doesn't match the QGrpcSerializationFormat::suffix of the specified QGrpcChannelOptions::serializationFormat QGrpcHttp2Channel produces warning.