-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
Launch AsyncAPI 2.0.0 #154
Comments
Could you please provide websocket examples. Totally misunderstand how to describe single channel like /ws with few subscribe/publish messages. |
Hi @vit1251. Can you please create an issue for that? This issue is completely unrelated and your question will be forgotten. Thanks! PS: I'll soon create guides on how to use AsyncAPI with different protocols and in different scenarios. |
@fmvilas hello, now I receive 2.0.0 pre-release update and you 20 day ago make a promise to provide WebSocket usage example. Do u provide WebSocket example with release or in documentation? It very important because I use WebSocket as event bus and exchange message right now |
Hey, @vit1251. I'll provide a good example using WebSockets soon. Sorry, I'm doing too many things. Don't worry, the spec is being tested in real scenarios and some of them include WebSockets. I just can't share them as they are internal APIs of the companies I work with. Again, I'll find time after the release to showcase different use cases and protocols. |
This issue serves as an "Epic" for the launch of AsyncAPI 2.0.0.
The text was updated successfully, but these errors were encountered: