Olà amigos! This is an exciting week for us. Solace joined the AsyncAPI Initiative as a Platinum Sponsor 🎉. Thank you, Jonathan Schabowsky, for leading the process. And if that’s not enough, we finished our “Protocol mappings” milestone. Keep reading!
Latest changes in the specification
Protocol-specific information. This is a long-awaited feature. It allows you to define protocol-specific information in channels, operations, and messages.
Separate application headers from protocol headers. From now on, all the protocol-related headers must be included in a
protocolInfoobject, and the existing messageheadersmust be used only for application headers, if any.Annotate a channel parameter as multi-level. Do you want to tell your code a specific parameter should span across multiple levels? Now you can annotate channel parameters to indicate that. Pretty much like the
#(pound) symbol in AMQP and MQTT or the>(greater than) symbol in NATS.Unify examples fields. In the past, we had the
examplefield in schemas and theexamplesfield in some other places of the specification. They are now unified using the plural form and allowing for more than an example per object. However, we didn’t remove the support forexamplefield in schemas, since we want to remain compatible with OpenAPI schemas.
Donate
And last but not least, we’ve completed our first three weeks running the sponsorship campaign. We greatly appreciate the support from Solace and look forward to working together. You’ll hear more exciting news in the upcoming weeks. Stay tuned!
Remember, we’ve got different tiers so that everybody can show their love! ❤️
Donate here. Help Open Source projects.
“Give yourself permission to slow down. You can speed up by slowing down.”
— Gabby Bernstein
See you next week, folks! 👋
Oldest comments (0)