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/b3a40f07-1817-43ce-841b-ab75db07849d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
