You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
How does another display learn about a change?
Reading the same address and receiving changes are separate steps.
Two displays show poll results. A participant votes and the business resource changes. Why does the second screen refresh? “They use the same address” is not a complete answer. Changes still need a route to the display.
One arrangement polls: request current results periodically. Another subscribes: a supporting implementation emits an event when a resource changes, and the consumer retrieves or applies updated content.
AFS subscription support is optional. Its capability information can describe spontaneous delivery, event types and whether events are session-scoped or visible across sessions. Consumers choose subscriptions or refresh behavior according to actual support.
| Layer | Work in the poll example |
|---|---|
| Business resource | Store the vote and resulting totals |
| Change propagation | Deliver supported notifications, or let a consumer read again |
| Interface connection | Supply the new results to the relevant binding or view |
| Display | Update its chart, table or text |
If presenter and audience reach the same results through different entry points, notifications must also reach the audience’s entry with resource addresses mapped accordingly. Otherwise, manually reading again could show fresh results while spontaneous updates never arrive.
To check reliability, observe the result on the second display and test recovery after disconnection. Audience members should still receive only content they are authorized to access.
Go deeper
Check your understanding
Do two displays reading the same results address prove live synchronization?
No. Verify change propagation, interface updates, access scope and reconnection behavior.
Continue along a learning path
- Take resources across boundariesStep 4 of 5