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.

Sign up for GitHub

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

Jump to bottom

Solve the channel reusability problem #73

Open
fmvilas opened this issue Mar 10, 2021 · 1 comment
Open

Solve the channel reusability problem #73

fmvilas opened this issue Mar 10, 2021 · 1 comment
Labels
Epic Solution A proposed solution that will help lead to the linked Key Result

Comments

@fmvilas
Copy link
Member

fmvilas commented Mar 10, 2021

Description

Reusing channels across APIs is hard because the publish or subscribe verb is included in the channel definition. We should come up with a way to decouple channel definition from the operation (publish/subscribe).

Previous work

@fmvilas created an issue here: asyncapi/spec#415.
@fmvilas fmvilas added Solution A proposed solution that will help lead to the linked Key Result Epic labels Mar 10, 2021
@fmvilas fmvilas changed the title Solve channel reusability problem Solve the channel reusability problem Mar 10, 2021
@smoya smoya mentioned this issue Mar 17, 2021
Closed
@smoya
Copy link
Member

smoya commented Mar 17, 2021

I emulated a breaking change on the spec for testing purposes and used this use case as an example. #93 (comment)

Please do not consider it as a very thorough solution since the purpose was not to solve this issue. However, it might be useful.

This was referenced Jul 21, 2021
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Epic Solution A proposed solution that will help lead to the linked Key Result
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fmvilas @smoya