-
Notifications
You must be signed in to change notification settings - Fork 55
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 binding for OpenMessaging specification #13
Comments
I would like to propose a simple http binding first. The main idea is simple, and the message model in OMS consist of four parts, I just map these parts into http protocol. The version is put in the url. The message headers are put in http header and prefixed with OMS. The user properties are put in the request headers, and the message body is in the http body and we set Content-Type to
|
At present, many message middlewares on the cloud provide http services, such as SNS, SQS in AWS, MNS in Alibaba Cloud, etc., with the rapid spread of http2, there will be more messaging services using http transmission in the future.
So many users hope that OpenMessaging can provide binding to the http message service to help users quickly access the messaging services of various vendors.
The text was updated successfully, but these errors were encountered: