Offers the components of an interface one board to tell what the system is doing and has done, wherever they sit
in the page: a component running an operation or catching an issue puts it up as a post without knowing who shows
it, and a component showing posts renders them, as a transient toast, a note in the page or a diagnostic panel,
without knowing who put them up, so concurrent sources never paint over one another.
Posts stand until they are cleared, and each keeps an identity of its own, so a source updates the post it put up
as its operation moves on, and a reader tells a new post from one it has already shown.
Issues nothing in the interface caught are taken up as well: a broken script and an unhandled rejection are raised
on the outermost board as they reach the page, so an exchange whose rejection went unattended is shown rather than
logged, and once only however many boards are nested, since no component inside any of them can claim it.
Posting and reading are offered apart, so a component only posting never renders because posts change.
Shared status board.
Offers the components of an interface one board to tell what the system is doing and has done, wherever they sit in the page: a component running an operation or catching an issue puts it up as a post without knowing who shows it, and a component showing posts renders them, as a transient toast, a note in the page or a diagnostic panel, without knowing who put them up, so concurrent sources never paint over one another.
Posts stand until they are cleared, and each keeps an identity of its own, so a source updates the post it put up as its operation moves on, and a reader tells a new post from one it has already shown.
Issues nothing in the interface caught are taken up as well: a broken script and an unhandled rejection are raised on the outermost board as they reach the page, so an exchange whose rejection went unattended is shown rather than logged, and once only however many boards are nested, since no component inside any of them can claim it.
Posting and reading are offered apart, so a component only posting never renders because posts change.