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.

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

Added new example 23 to check mixed of communications #244

Merged

Conversation

aregtech
Copy link
Owner

@aregtech aregtech commented Sep 1, 2023

There were several fixes in previous commits. In order to check the communication and fixes, created 2 new examples to demonstrate the data update notifications. All checks prove that communication work fine. The minor issue, which is neither a bug, nor features:

  • When the service consumer looses network connection, the data (attribute) of the remote service is not automatically marked as invalid. One side, this may keep the information of the last available status. On the hand, since it is unknown how long the connection is lost, it might make sense to invalidate the data on Consumer side.

In addition, made changes in Makefile. Make it more clear.

Copy link
Collaborator

@vukihub vukihub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. The documents should be updated.

@aregtech aregtech merged commit 07d69ac into master Sep 2, 2023
36 checks passed
@aregtech aregtech deleted the bugfix/239-consumers-are-not-notified-on-first-subscription branch October 4, 2023 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Reviewed
Development

Successfully merging this pull request may close these issues.

Consumers are not notified on first subscription
2 participants