hpvd opened a new issue #8701: URL: https://github.com/apache/pulsar/issues/8701
extracted from: https://github.com/apache/pulsar/issues/2678#issuecomment-733220888 **Is your feature request related to a problem? Please describe.** imho websocket is for pulsar something like "the window to the website world". It enables usage of pulsar for fields like web-tracking, live chat and many more... If one see the potential of this community, one should give websocket bugs and feature-requests a fair priority in the next releases While writing this there are roughly 25 issues open regarding websocket topics. https://github.com/apache/pulsar/issues?q=is%3Aissue+is%3Aopen+websocket+ 3 includes open pull request which may be easy to close. **Describe the solution you'd like** Of course recourses are limited and not all fields have the same importance for adoption of pulsar. But at least the points - docs e.g. https://github.com/apache/pulsar/issues/8610, https://github.com/apache/pulsar/issues/8688 - security e.g. https://github.com/apache/pulsar/issues/3493 - performance e.g. https://github.com/apache/pulsar/issues/8584, https://github.com/apache/pulsar/issues/5979 are important for everyone thinking about using pulsar with websocket.. With this said I would vote for the mid-term goal already named 2018 in https://github.com/apache/pulsar/issues/2678 "websocket feature parity" (as far as technical possible..) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
