-
Notifications
You must be signed in to change notification settings - Fork 9
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
Intents should be transported to subscribed microfrontends only #124
Labels
Comments
danielwiehl
added a commit
that referenced
this issue
Oct 21, 2022
Previously, an intent was transported to all qualified clients regardless of whether the client had a subscription for the intent, causing unnecessary messaging delivery and is a prerequisite for supporting retained intents. closes #124
danielwiehl
added a commit
that referenced
this issue
Oct 21, 2022
Previously, an intent was transported to all qualified clients regardless of whether the client had a subscription for the intent, causing unnecessary messaging delivery and is a prerequisite for supporting retained intents. closes #124
danielwiehl
added a commit
that referenced
this issue
Oct 25, 2022
Previously, an intent was transported to all qualified clients regardless of whether the client had a subscription for the intent, causing unnecessary messaging delivery and is a prerequisite for supporting retained intents. closes #124
danielwiehl
added a commit
that referenced
this issue
Oct 25, 2022
Previously, an intent was transported to all qualified clients regardless of whether the client had a subscription for the intent, causing unnecessary traffic on the message bus and is a prerequisite for supporting retained intents. closes #124
danielwiehl
added a commit
that referenced
this issue
Oct 25, 2022
Previously, an intent was transported to all qualified clients regardless of whether the client had a subscription for the intent, causing unnecessary traffic on the message bus and is a prerequisite for supporting retained intents. closes #124
danielwiehl
added a commit
that referenced
this issue
Oct 26, 2022
Previously, an intent was transported to all qualified clients regardless of whether the client had a subscription for the intent, causing unnecessary traffic on the message bus and is a prerequisite for supporting retained intents. closes #124
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Applications typically subscribe to intents in activator microfrontends. However, intents are broadcasted to each loaded microfrontend of the providing application, which causes unnecessary traffic on the messaging bus, especially when many microfrontends of that application are loaded.
Describe the solution you'd like
Intents should only be transported to microfrontends that have a respective subscription, thus analogous to topic subscriptions, where messages are transported to subscribed microfrontends only.
The text was updated successfully, but these errors were encountered: