-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binary protocol documentation #109
Labels
doc
Your PR contains doc changes, no matter whether the changes are in markdown or code files.
Milestone
Comments
merlimat
added
the
doc
Your PR contains doc changes, no matter whether the changes are in markdown or code files.
label
Nov 14, 2016
Good point. Documenting the binary protocol was on the TODO list although got pushed over a bit. I'll try to get a it shortly. |
Thanks! |
sijie
pushed a commit
to sijie/pulsar
that referenced
this issue
Mar 4, 2018
hrsakai
pushed a commit
to hrsakai/pulsar
that referenced
this issue
Dec 10, 2020
…r. (apache#109) * Fix subscriber bug and use Consumer interface for multi topic consumer. * Remove consumer copy when setting up multi and regex consumer.
massakam
pushed a commit
to massakam/pulsar
that referenced
this issue
Feb 9, 2021
hangc0276
pushed a commit
to hangc0276/pulsar
that referenced
this issue
May 26, 2021
* change place of scripts/dev/get-project-version.py * add release link in readme
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
doc
Your PR contains doc changes, no matter whether the changes are in markdown or code files.
I saw a websocket docs around, but apart from reading the proto and source, is there any plans to expose and document the binary protocol? Websockets are nice and all, but documented binary protocol could allow for more community client libraries.
The text was updated successfully, but these errors were encountered: