[GitHub] cbornet commented on issue #271: Consider using gRPC as an externally exposed API

cbornet commented on issue #271: Consider using gRPC as an externally exposed API URL: https://github.com/apache/pulsar/issues/271#issuecomment-440419313 Yes. That's a very good reason indeed. Maybe in the future 😄 . I can understand there are bigger priorities. --

[GitHub] cbornet commented on issue #271: Consider using gRPC as an externally exposed API

cbornet commented on issue #271: Consider using gRPC as an externally exposed API URL: https://github.com/apache/pulsar/issues/271#issuecomment-440384538 And if I'm not mistaken BookKeeper uses gRPC internally, so it would be coherent to make it the base protocol in Pulsar also. -

[GitHub] cbornet commented on issue #271: Consider using gRPC as an externally exposed API

cbornet commented on issue #271: Consider using gRPC as an externally exposed API URL: https://github.com/apache/pulsar/issues/271#issuecomment-440381769 > One of the primary goals of the custom binary protocol we came up with, was to have the client establish a "session" (either producer

[GitHub] cbornet commented on issue #271: Consider using gRPC as an externally exposed API

cbornet commented on issue #271: Consider using gRPC as an externally exposed API URL: https://github.com/apache/pulsar/issues/271#issuecomment-436952546 +1. Supporting gRPC would give access to a lot more clients, integration with reactive frameworks (like RxJava or Reactor), provide appl