Skip to content
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

HTTP and HTTPS schemes are missing #81

Closed
fmvilas opened this issue Jul 18, 2018 · 5 comments
Closed

HTTP and HTTPS schemes are missing #81

fmvilas opened this issue Jul 18, 2018 · 5 comments

Comments

@fmvilas
Copy link
Member

fmvilas commented Jul 18, 2018

HTTP and HTTPS schemes are missing in human-readable documentation, i.e., in the README.

@mattheworiordan
Copy link

mattheworiordan commented Sep 2, 2018

What is HTTP and HTTPS as a scheme in regards to AsyncAPI? Specifically, HTTP is a request/response mechanism, so how would a client generically use HTTP and HTTPS as a transport and scheme for a message oriented connection?

@fmvilas
Copy link
Member Author

fmvilas commented Sep 2, 2018

We also support streaming APIs since version 1.2.0: https://github.com/asyncapi/asyncapi#streamObject.

Check out this example: https://github.com/asyncapi/asyncapi/blob/v2/test/docs/gitter-streaming.yaml

@vadeg
Copy link

vadeg commented Sep 24, 2018

@fmvilas Could you please clarify when version 1.3.0 will be released?

@fmvilas
Copy link
Member Author

fmvilas commented Sep 25, 2018

I'd like to have a date @vadeg, but lately I'm trying to setup a core group to keep improving AsyncAPI and don't have so much time for coding right now.

Will keep you informed when it's decided. Thanks!

@fmvilas
Copy link
Member Author

fmvilas commented Feb 21, 2019

Closing as it's already fixed in #151.

@fmvilas fmvilas closed this as completed Feb 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants