Thanks Ken. So, it is probably useful for quickly prototyping application logic or write some quick tests for the new applications ? As a piped pair of endpoints will eliminate the need of a separate external grpc server(or client).
On Thursday, February 22, 2018 at 12:24:03 AM UTC+5:30, Ken Payson wrote: > > Behind the scenes, *grpc_iomgr_create_endpoint_pair*( ) creates a unix > socketpair instead of the standard connected socket. > > The endpoint pair is already piped when it is returned. Socketpairs can > be a useful alternative to standard sockets if your client/server are both > in the same process. > > On Tuesday, February 20, 2018 at 9:32:19 PM UTC-8, dharam...@cypress.com > wrote: >> >> >> Hi, >> I've a pretty basic question regarding the implementation of >> *grpc_iomgr_create_endpoint_pair*( ). >> >> For Posix/Windows environment, it returns a pair of endpoints(client & >> server). >> >> My questions , in general, is about understanding the purpose of an >> end-point pair? Main confusion is around these endpoints getting internally >> piped before being returned ? >> >> If end-point/sockets represent the remote device, should it be >> piped/connected to another local socket? >> >> >> Br, >> Dharam >> > -- 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 grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. 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/fb57708a-7500-4eb8-a38e-35aa48c2ef6f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
