Eanble the association of channels with servers/brokers

[bruno-baloi-mulesoft]

There is a significant need for the ability to design Async APIs that perform multiple activities.

For instance consuming events over one type of transport/server (i.e. MQTT) and subsequently generating events over other types of transports (i.e. AMQP). Typically if an Async API implements some type of event choreography that occurs quite often. Additionally there can be APIs that act as Transport bridges and applying certain types event filtering or processing.

In these types of scenarios the Async API spec will need to define the servers, and the channels need to have a mechanism whereby they can indicate what server they are bound to.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue.

Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[fmvilas]

Duplicate of #255?

[bruno-baloi-mulesoft]

Thx Fran. So can we expect the update to the spec then ?

[fmvilas]

I'm working on the roadmap for 2.1.0. Don't have a date yet but will update here as soon as we know. Thanks for your patience.