At the end of stage 4 we noted that the updater experiences two refreshes of the table upon any update – one due to the built-in refresh process in each of the buttons ('New', 'Update' or 'Delete'), and one due to the subscription to updates. We said that to overcome this problem, user subscriptions to updates should ignore updates made by themselves.
Let's do it now.
We'll use the 'Source' field of the publish-subscribe message to identify the publisher of each change. Thus the publisher "signs" any change message he/she publishes, and the subscribers will ignore any message signed by themselves.
Here is a possible way to model this behavior:
Download Model: Stage 9 (version 2.4.1)
For best results, use the Firefox browser..