You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/06/06 08:17:55 UTC

[GitHub] [pulsar] mattisonchao commented on pull request #15942: [feature][broker] Support HTTP endpoint consume messages

mattisonchao commented on PR #15942:
URL: https://github.com/apache/pulsar/pull/15942#issuecomment-1147178378

   > It might not be a good idea to add the implementation to the main Pulsar Admin API at all.
   > 
   > HTTP consuming would be better to handle in a separate component. PIP-64 doesn't determine that this should be part of Pulsar Admin API and we should revisit this decision. I think it's a bad idea to add HTTP consuming to Pulsar Admin API and brokers.
   > 
   > We need another discussion on the dev mailing list for deciding.
   
   Yes, I also consider moving this part of the HTTP producer-consumer to pulsar-proxy, which will make the broker clear and reduce communication between brokers.
   However, moving this part to the pulsar proxy will require the user to deploy another component, especially if the user is not running the pulsar in k8s.
   
   I will draft a discussion in the dev mail list.
   
   
   Best,
   Mattison
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org