Cross-referencing a PR in nanopb to add gRPC support: https://github.com/nanopb/nanopb/pull/248.
On Monday, December 11, 2017 at 11:44:32 AM UTC+1, [email protected] wrote: > > Thanks Craig for your comments, > > Seems reasonable and at least we're aligned. The idea of this thread was > to know how open the grpc community would be to create an entrypoint to > solve existing issues with these kind of transports (although transport in > gRPC refers to application-level transport i.e h2, grpc-web, ...). I would > like to start discussing the hows and put some on the table in order to > push this forward, we're really interested to have an upstreamed solution. > > WDYT if we start with the C based gRPC codebase, can you extend your idea > on publishing grpc_endpoint with some pseudocode? > > On Wednesday, December 6, 2017 at 2:44:25 AM UTC+1, Craig Tiller wrote: >> >> For common things (Bluetooth, websockets) I think having these available >> by default for all core languages could make sense. >> >> For Bluetooth I could imagine a bluetooth:// naming scheme, and for >> websockets a handshaker and wrapped endpoint that's toggled on via a >> channel arg? >> > -- 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/c110ef2a-8820-48e3-8799-cfc4de47d72d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
