person to
> > maintain the protocol handler. You can grow the community for a given
> > protocol handler as well. It is how we build and maintain KoP, AoP,
> > and MoP.
> >
> > 2. gRPC isn't a zero-copy protocol. It is not well suited for
> > implementing
;t a zero-copy protocol. It is not well suited for
> implementing high-throughput streaming services.
>
> 3. Unlike KoP, MoP and AoP which are implementing well-known messaging
> protocols, the gRPC protocol handler is not an extension to support a
> different protocol. It is essentially
gRPC isn't a zero-copy protocol. It is not well suited for
implementing high-throughput streaming services.
3. Unlike KoP, MoP and AoP which are implementing well-known messaging
protocols, the gRPC protocol handler is not an extension to support a
different protocol. It is essentially re-im
streaming products
like Kafka and AMQP.
I’ve created a PIP
<https://github.com/apache/pulsar/wiki/PIP-59%3A-gPRC-Protocol-Handler> and
an implementation of a gRPC protocol handler, but review of the pull
request stalled out <https://github.com/apache/pulsar/pull/6512> so I moved
my imple
#x27;d like to propose the following PIP on a gRPC protocol handler :
> https://gist.github.com/cbornet/f0a18c4528c2be129bb120cc231b62c6
> See https://github.com/apache/pulsar/issues/271 for a discussion on having
> gRPC as an alternative protocol for Pulsar.
> I also have a MVP of the
Dear Pulsar team,
I'd like to propose the following PIP on a gRPC protocol handler :
https://gist.github.com/cbornet/f0a18c4528c2be129bb120cc231b62c6
See https://github.com/apache/pulsar/issues/271 for a discussion on having
gRPC as an alternative protocol for Pulsar.
I also have a MVP o
