Nicolas, Thank you for the answer Currently, chttp2 transport operates with only one tcp_endpoint. What if I implemented second endpoint, based on other network HW (Infiniband). In this case, chttp2 could operate with two different endpoints and have to select proper endpoint for incoming connection (on server side). What is why I asked about "additional fields" in http. I would understand how to implement endpoint selector algorithm properly. I would provide the code which allow gRPC server works with tcp_endpoint clients and ucx_endpoint (my endpoint) clients simultaneously.
Sergey On Wednesday, September 7, 2016 at 8:31:45 PM UTC+3, Nicolas Noble wrote: > > Transports need to be supplied the proper endpoint, and not the other way > around. So the idea is that you can supply your own endpoints to the C core > if you want when calling into grpc_create_chttp2_transport. See for example > channel_create.c - you could write your own channel code that'll spawn > whichever endpoint you want and then plumb into chttp2. > > On Monday, September 5, 2016 at 2:27:59 AM UTC-7, Sergey Shalnov wrote: >> >> Hi, >> I would like to understand how to select gRPC endpoint dynamically. As I >> can see, chttp2 uses tcp_endpoint for this time only. >> Should I add some additional fields into chttp2 metadata to establish >> connection with desired endpoint properly? >> Thank you >> Sergey > > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5ac16b61-c841-4b5d-b68c-a1ed81ffecb4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
