The C# behavior here would be exactly the same as for all other implementations based on C-core.
I don't think currently there's any way of expressing that some HTTP/2 streams should be prioritized over others (and there are no plans that I know of to implement that) On Wednesday, July 24, 2019 at 8:05:48 PM UTC-7, Sam wrote: > > Hi all, > > It seems that there's already a small discussion about streaming priority, > last august: https://github.com/grpc/grpc-go/issues/1448 > > Are there any updates for this ? especially concerning the C# wrapper. > > If not, I'm curious as to what actually happens when I use the > *WriteAsync()* on the stream call. It hands off the work to gRPC, and I'm > wondering what rules/logic gRPC follows to multiplex the messages (even a > rough, inaccurate description would be nice, just to get the idea). I have > multiple streams, written to concurrently + normal unary calls. Especially > I would like to know if the order in which *WriteAsync() *is called has > any influence on send order. > > Is there currently any way I can prioritize certain streams/message types > ? If not, any plans to support ? > > Thanks, > Sam > -- 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/d7b7dfe4-95d9-411f-8638-07cc1fb20b95%40googlegroups.com.
