On Mon, Nov 2, 2020 at 10:39 PM Avinash Lakshman <[email protected]> wrote:
> I was just looking at this as an academic exercise given the literature > says that the transport is pluggable. > What literature is that? Yes I would be looking at the client and server side. > So transport is pluggable in two ways: 1) you can implement ManagedChannel and Server directly or 2) you can use ManagedChannelImpl and ServerImpl as utilities and then implement the transport that they expect. (1) basically implements "all the hard parts of gRPC". (2) is still involved, but some things like load balancing and service config would be handled for you. (2) is typically what we mean by "implementing a transport". The precise details change a bit depending on what type of transport you want to implement. For example, InProcess is dramatically different than OkHttp and Netty. What transport do you want to implement? -- 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/CA%2B4M1oMHA-_kurh%2Bwz4U4CjuH0STSQQFLveXmBUKh11WOA0vog%40mail.gmail.com.
smime.p7s
Description: S/MIME Cryptographic Signature
