+1 Feature parity between different pulsar clients will surely benefit from this. Java client, for instance, is generally ahead of other languages. If we can have a rest api for streaming, one could just add a feature there and have all the clients unblocked.
Regards, Shivji Kumar Jha http://www.shivjijha.com/ +91 8884075512 On Wed, May 13, 2020 at 3:55 PM Sijie Guo <si...@apache.org> wrote: > Hi all, > > Some of the people have been asking for a REST-proxy like equivalent > component in Pulsar. Pulsar already has a web service that provides the > management API over a Pulsar cluster. We don't actually need a separate > component or service for supporting streaming events in and out of Pulsar > using HTTP. We can just add endpoints to the existing web server to support > those functionalities. > > I'd like to start a discussion on adding REST endpoints to the current web > server for producing, consuming and reading messages. So people can use > HTTP for streaming events in and out of Pulsar without setting up > additional components. > > The full proposal is written at > > https://github.com/apache/pulsar/wiki/PIP-64:-Introduce-REST-endpoints-for-producing,-consuming-and-reading-messages > . > > Feedback and comments are welcome! > > - Sijie >
