Currently I use the JsonHttpClient in my cross platform solution with the HttpMessageHandler property where I use the NativeMessageHandler so that I can for instance use the native OKHttp3 on Xamarin Forms Android. Is there an option to use something like this in gRPC ? If not how does this work on XF android for instance.
Lastly, gRPC Server Send Events does not have a fallback as is the case with gRPC and REST. Any plans in future to give us an equivalent fallback on basic functionality like channels / triggers ? So for clarity where you can define one endpoint for SSE that will include both gRPC and REST. Obviously only where the functionality overlap.
thanks @mythz. When you generate the protoc files , is there no way to then “flag” the rest endpoint so that it can be displayed in the metadata page. visually it will be much easier to check ;))
If I follow you correctly then there should be no reason to use any HttpMessageHandler to increase performance as it’s already using custom clients (Grpc.Core, Grpc.Net.Client & protobuf-net.Grpc) that should work great especially when .net 5 arrives and use the same BCL as .net core 3.0
No there shouldn’t be any need to interfere with the gRPC communication implementation as they’re developed to use an efficient HTTP/2 persistent channel.
The issue with the metadata page is that all gRPC Server implementation is in a .NET Core 3. ServiceStack.Extensions project what ServiceStack’s metadata pages don’t have a reference to, there’s also no additional information we could show about a gRPC service only that it’s available via gRPC.