websocket feature parity

[sfescape]

Is there a roadmap that discusses websocket features? It looks like websockets is pretty far behind in feature parity.
I'm considering moving from kafka to pulsar but topics regex consumer is an important feature for me.

[hpvd]

feature parity would indeed be pretty awesome and would imho help adoption further

[hpvd]

for latest state see: https://github.com/apache/pulsar/wiki/Client-Features-Matrix

[hpvd]

imho websocket is for pulsar something like "the window to the web 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.

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. Enrich the usage of Websocket in Pulsar docs #8610, [Doc]Contradictory documentation of websocket features #8688
• security e.g. Security Vulnerabilities - Black Duck Scan #3493
• performance e.g. WebSocket broker: url (path and query) args (namespace, topic, etc...) exposed through message fields #8584, Websocket API should support cumulative acknowledgement #5979

are important for everyone thinking about using pulsar with websocket..