DEV Community

Cover image for Status update (week 11, 2019)
Fran Méndez 🍺
Fran Méndez 🍺

Posted on

Status update (week 11, 2019)

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

  1. Protocol-specific information. This is a long-awaited feature. It allows you to define protocol-specific information in channels, operations, and messages.

  2. Separate application headers from protocol headers. From now on, all the protocol-related headers must be included in a protocolInfo object, and the existing message headers must be used only for application headers, if any.

  3. 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.

  4. Unify examples fields. In the past, we had the example field in schemas and the examples field 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 for example field in schemas, since we want to remain compatible with OpenAPI schemas.

Cumulative flow chart showing the progress of AsyncAPI 2.0.0.

Cumulative flow chart showing the progress of AsyncAPI 2.0.0.

Release report showing the planned and predicted end dates. We’re 38 days ahead of plan! 🔥

Release report showing the planned and predicted end dates. We’re 38 days ahead of plan! 🔥

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! 👋

Top comments (3)

Collapse
 
jameswebber profile image
James Webber

The Status Check is a valuable tool for beneficiaries, as it provides them with real-time updates on the status of their payments. By anticipating the exact disbursement dates, beneficiaries can effectively plan their monthly finances and avoid unexpected financial burdens. This feature is particularly helpful for those who rely heavily on SASSA payments to meet their essential needs. With the Srd SASSA Status Check, beneficiaries can ensure that they have sufficient funds to cover their expenses, such as rent, utilities, and groceries, without experiencing undue stress or financial hardship.

Collapse
 
saadkaleem123 profile image
saad kaleem • Edited

This week brings exciting news as Solace joined the AsyncAPI Initiative as a Platinum Sponsor 🎉. Big thanks to Jonathan Schabowsky for leading the way. We also completed the "Protocol mappings" milestone, introducing features like defining protocol-specific information, separating application and protocol headers, and annotating multi-level channel parameters. We unified the example fields to allow more examples per object, while maintaining compatibility with OpenAPI schemas. Stay tuned for more updates, and don't forget to check out the latest progress, just like you would with a SASSA status check

Collapse
 
debin_alsa_8889667525d557 profile image
Debin Alsa

Regularly checking the status provides information on the disbursement dates of payments. Beneficiaries can know when to expect their funds SASSA Status Check, which aids in planning and budgeting their monthly expenses.