>
> If this is a REST endpoint then call it REST. It is very likely that users
> will want to use HTTPS to use it. Calling it HTTP is a misnomer.
Very thanks for your correction.
Best,
Mattison
On Thu, 9 Jun 2022 at 15:37, mattison chao wrote:
> I think building a separate HTTP server to
>
> I think building a separate HTTP server to serve REST produce/consume
> requests might be a good idea, like FunctionWorkerService, users can choose
> to run with broker for simplicity or run as a separate component if user
> wants isolation and scale independently.
Yes, it's a great
I would make a separate project and release it as a .nar. It can run as a
Broker Protocol Handler or a Proxy Extension.
Then if the project gets traction we can add it to Pulsar core repo.
Enrico and
Il Mar 7 Giu 2022, 17:05 Dave Fisher ha scritto:
> If this is a REST endpoint then call it
If this is a REST endpoint then call it REST. It is very likely that users will
want to use HTTPS to use it. Calling it HTTP is a misnomer.
All The Best,
Dave
Sent from my iPhone
> On Jun 7, 2022, at 7:25 AM, Zhengxin Cai wrote:
>
> Thanks for bringing this up.
> I think building a separate
Thanks for bringing this up.
I think building a separate HTTP server to serve REST produce/consume
requests might be a good idea, like FunctionWorkerService, users can choose
to run with broker for simplicity or run as a separate component if user
wants isolation and scale independently.
I think
Hi, Pulsar Community,
We have the PIP-64 that introduces HTTP Rest API for producing/consuming
messages(
https://github.com/apache/pulsar/wiki/PIP-64%3A-Introduce-REST-endpoints-for-producing%2C-consuming-and-reading-messages
). But this proposal does not define the implementation.
However, we
