Parts V to IX in the book, extension 2.9.1, Demo topics
Add chapters 05-08 to the three language profiles: the published book stopped at Part IV because only 00-04 were listed. Rename the MQTT topic root Tutorial/ to Demo/ in Part IX (code and output included). Shared notes extension 2.9.1: dependency folders are named after the extension version, so browsers stop serving stale scripts after an update. Full rebuild of _book/ (HTML and PDF, three languages); remove the stray site_libs/ that the last Deploy commit had added at the project root. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
1 parent
01f681165f
commit
f047b9c7ae
128 files changed
+18893
-7591
No files matched your search
+37
-13
@@ -52,19 +52,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -510,6 +510,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Part IV — Rewind</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Part V — Replay the dynamic idea across processes</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Part VI — Replay it over Syncthing, and name the messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Part VII — Now merge the two architectural ideas</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Part IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
+37
-13
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Part IV — Rewind</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Part V — Replay the dynamic idea across processes</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Part VI — Replay it over Syncthing, and name the messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Part VII — Now merge the two architectural ideas</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Part IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Part IV — Rewind</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Part V — Replay the dynamic idea across processes</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Part VI — Replay it over Syncthing, and name the messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Part VII — Now merge the two architectural ideas</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Part IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -52,19 +52,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -510,6 +510,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Part IV — Rewind</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Part V — Replay the dynamic idea across processes</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Part VI — Replay it over Syncthing, and name the messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Part VII — Now merge the two architectural ideas</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Part IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -71,7 +71,7 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<script src="site_libs/quarto-search/fuse.min.js"></script>
|
||||
<script src="site_libs/quarto-search/quarto-search.js"></script>
|
||||
<meta name="quarto:offset" content="./">
|
||||
<link href="./glossary.html" rel="next">
|
||||
<link href="./05-part-v-subscriptions.html" rel="next">
|
||||
<link href="./03-part-iii-distributed.html" rel="prev">
|
||||
<script src="site_libs/quarto-html/quarto.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/tabsets/tabsets.js" type="module"></script>
|
||||
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link active">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Part IV — Rewind</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Part V — Replay the dynamic idea across processes</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Part VI — Replay it over Syncthing, and name the messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Part VII — Now merge the two architectural ideas</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Part IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -631,7 +655,7 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<section id="sec-route-topic-intent" class="level2" data-number="5.4">
|
||||
<h2 data-number="5.4" class="anchored" data-anchor-id="sec-route-topic-intent"><span class="header-section-number">5.4</span> <code>ROUTE</code> and <code>TOPIC</code> are Intent</h2>
|
||||
<p>Apply two tests to <code>TOPIC consoleIn.outbox</code>. Does it describe something that happened? No. Something currently true? No. It says <em>please begin listening here</em> — desired behaviour, which is <strong>Intent</strong>. The mediator’s <code>ROUTE</code> is the same kind of message: <em>please forward from here to there</em>.</p>
|
||||
<p>One trap worth naming, because it is tempting in a defence: <em>publishing</em> an Intent is of course something that happened. Classification follows what the message says, not the fact that it exists.</p>
|
||||
<p>One trap worth naming, because it is tempting in a defence: <em>publishing</em> an Intent is naturally something that happened. Classification follows what the message says, not the fact that it exists.</p>
|
||||
<p>And one condition, which returns later: the dynamic version is <strong>not</strong> automatically superior. It makes sense only if the consumer actually understands the producer’s message contract.</p>
|
||||
<pre class="text"><code>STATIC MEDIATED DYNAMIC DIRECT
|
||||
Producer → Mediator → Consumer Intent → (Producer ──► Consumer)</code></pre>
|
||||
@@ -1281,8 +1305,8 @@ Producer → Mediator → Consumer Intent → (Producer ──► Consumer)</c
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-page nav-page-next">
|
||||
<a href="./glossary.html" class="pagination-link" aria-label="[Glossary]{.en}[Glossaire]{.fr}[Glossar]{.de}">
|
||||
<span class="nav-page-text">Glossary</span> <i class="bi bi-arrow-right-short"></i>
|
||||
<a href="./05-part-v-subscriptions.html" class="pagination-link" aria-label="[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}">
|
||||
<span class="nav-page-text"><span class="chapter-number">6</span> <span class="chapter-title">Part V — Replay the dynamic idea across processes</span></span> <i class="bi bi-arrow-right-short"></i>
|
||||
</a>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
Binary file not shown.
@@ -52,19 +52,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -510,6 +510,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Teil IV — Zurückspulen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Teil V — Die dynamische Idee über Prozesse hinweg wiederholen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Teil VI — Über Syncthing wiederholen und die Nachrichten benennen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Teil VII — Die zwei architektonischen Ideen zusammenführen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Teil IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Teil IV — Zurückspulen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Teil V — Die dynamische Idee über Prozesse hinweg wiederholen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Teil VI — Über Syncthing wiederholen und die Nachrichten benennen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Teil VII — Die zwei architektonischen Ideen zusammenführen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Teil IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Teil IV — Zurückspulen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Teil V — Die dynamische Idee über Prozesse hinweg wiederholen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Teil VI — Über Syncthing wiederholen und die Nachrichten benennen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Teil VII — Die zwei architektonischen Ideen zusammenführen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Teil IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -52,19 +52,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -510,6 +510,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Teil IV — Zurückspulen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Teil V — Die dynamische Idee über Prozesse hinweg wiederholen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Teil VI — Über Syncthing wiederholen und die Nachrichten benennen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Teil VII — Die zwei architektonischen Ideen zusammenführen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Teil IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -71,7 +71,7 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<script src="site_libs/quarto-search/fuse.min.js"></script>
|
||||
<script src="site_libs/quarto-search/quarto-search.js"></script>
|
||||
<meta name="quarto:offset" content="./">
|
||||
<link href="./glossary.html" rel="next">
|
||||
<link href="./05-part-v-subscriptions.html" rel="next">
|
||||
<link href="./03-part-iii-distributed.html" rel="prev">
|
||||
<script src="site_libs/quarto-html/quarto.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/tabsets/tabsets.js" type="module"></script>
|
||||
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link active">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Teil IV — Zurückspulen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Teil V — Die dynamische Idee über Prozesse hinweg wiederholen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Teil VI — Über Syncthing wiederholen und die Nachrichten benennen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Teil VII — Die zwei architektonischen Ideen zusammenführen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Teil IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -1281,8 +1305,8 @@ Produzent → Vermittler → Konsument Intent → (Produzent ──► Konsume
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-page nav-page-next">
|
||||
<a href="./glossary.html" class="pagination-link" aria-label="[Glossary]{.en}[Glossaire]{.fr}[Glossar]{.de}">
|
||||
<span class="nav-page-text">Glossar</span> <i class="bi bi-arrow-right-short"></i>
|
||||
<a href="./05-part-v-subscriptions.html" class="pagination-link" aria-label="[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}">
|
||||
<span class="nav-page-text"><span class="chapter-number">6</span> <span class="chapter-title">Teil V — Die dynamische Idee über Prozesse hinweg wiederholen</span></span> <i class="bi bi-arrow-right-short"></i>
|
||||
</a>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
Binary file not shown.
+40
-16
@@ -36,7 +36,7 @@ ul.task-list li input[type="checkbox"] {
|
||||
<script src="site_libs/quarto-search/fuse.min.js"></script>
|
||||
<script src="site_libs/quarto-search/quarto-search.js"></script>
|
||||
<meta name="quarto:offset" content="./">
|
||||
<link href="./04-part-iv-rewind.html" rel="prev">
|
||||
<link href="./08-part-ix-mqtt.html" rel="prev">
|
||||
<script src="site_libs/quarto-html/quarto.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/tabsets/tabsets.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/popper.min.js"></script>
|
||||
@@ -51,19 +51,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -509,6 +509,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Teil IV — Zurückspulen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Teil V — Die dynamische Idee über Prozesse hinweg wiederholen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Teil VI — Über Syncthing wiederholen und die Nachrichten benennen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Teil VII — Die zwei architektonischen Ideen zusammenführen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Teil IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -1211,8 +1235,8 @@ Every entry here is defined in the chapter where the term first does some
|
||||
</script>
|
||||
<nav class="page-navigation">
|
||||
<div class="nav-page nav-page-previous">
|
||||
<a href="./04-part-iv-rewind.html" class="pagination-link" aria-label="[Part IV — Rewind]{.en}[Partie IV — Rembobinage]{.fr}[Teil IV — Zurückspulen]{.de}">
|
||||
<i class="bi bi-arrow-left-short"></i> <span class="nav-page-text"><span class="chapter-number">5</span> <span class="chapter-title">Teil IV — Zurückspulen</span></span>
|
||||
<a href="./08-part-ix-mqtt.html" class="pagination-link" aria-label="[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}">
|
||||
<i class="bi bi-arrow-left-short"></i> <span class="nav-page-text"><span class="chapter-number">9</span> <span class="chapter-title">Teil IX — MQTT</span></span>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-page nav-page-next">
|
||||
|
||||
+38
-14
@@ -52,19 +52,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -510,6 +510,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Teil IV — Zurückspulen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Teil V — Die dynamische Idee über Prozesse hinweg wiederholen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Teil VI — Über Syncthing wiederholen und die Nachrichten benennen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Teil VII — Die zwei architektonischen Ideen zusammenführen</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Teil IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -568,7 +592,7 @@ ul.task-list li input[type="checkbox"] {
|
||||
<div>
|
||||
<div class="quarto-title-meta-heading">Veröffentlichungsdatum</div>
|
||||
<div class="quarto-title-meta-contents">
|
||||
<p class="date">6 Oktober 2026</p>
|
||||
<p class="date">16 Oktober 2026</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
@@ -329,6 +329,236 @@
|
||||
"<span class='chapter-number'>5</span> <span class='chapter-title'>[Part IV — Rewind]{.en}[Partie IV — Rembobinage]{.fr}[Teil IV — Zurückspulen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html",
|
||||
"href": "05-part-v-subscriptions.html",
|
||||
"title": "6 Teil V — Die dynamische Idee über Prozesse hinweg wiederholen",
|
||||
"section": "",
|
||||
"text": "6.1 Ein blockierendes watch genügt nicht\nDie Schritte 35 bis 38 holen die Abonnement-Idee aus der einzelnen JVM heraus. Die Dienste werden wieder getrennte Programme, aber anstelle von Vermittlern, die Dateien kopieren, beobachtet jeder Dienst das Postfach, das ihm gesagt wurde. Eine Annahme des ersten Dateisystem-Helfers übersteht den Umzug nicht, und genau deren Korrektur ist das Thema dieses Teils.\nFileMessageBoard.watch(topic, receiver) registriert ein Verzeichnis und blockiert für immer. Das genügte, solange jeder Prozess ein festes Postfach beobachtete. Ein dynamisch verdrahteter Dienst braucht mehr:\nDie alte Signatur kann das nicht ausdrücken, und die Folge war schon vorher sichtbar: der konfigurierbare Vermittler nahm genau eine ROUTE an, denn sobald er seine Quelle beobachtete, wurde er für sein eigenes Steuerpostfach taub. Die Grenze war nie, wessen Verzeichnis es ist — sondern eines, festes, für immer.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-watch-limit",
|
||||
"href": "05-part-v-subscriptions.html#sec-watch-limit",
|
||||
"title": "6 Teil V — Die dynamische Idee über Prozesse hinweg wiederholen",
|
||||
"section": "",
|
||||
"text": "dauerhaft das eigene Steuerpostfach beobachten\nUND\nzur Laufzeit ein beobachtetes Verzeichnis hinzufügen\nUND\nes möglicherweise später entfernen",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-filesubscriptions",
|
||||
"href": "05-part-v-subscriptions.html#sec-filesubscriptions",
|
||||
"title": "6 Teil V — Die dynamische Idee über Prozesse hinweg wiederholen",
|
||||
"section": "6.2 Der Helfer: FileSubscriptions",
|
||||
"text": "6.2 Der Helfer: FileSubscriptions\nEin WatchService kann viele Verzeichnisse bedienen. register(...) gibt einen WatchKey zurück, der eines davon bezeichnet, watcher.take() liefert den Schlüssel mit Ereignissen, und key.cancel() meldet ihn ab. Der Helfer hält beide Richtungen, Name → Schlüssel und Schlüssel → Name, damit ein Ereignis auf das Postfach zurückgeführt werden kann, aus dem es kam.\nEreignisse erreichen keinen Callback direkt. Sie gehen in eine Warteschlange, gelesen mit take(), und tragen\nrecord IncomingMessage(String mailbox, Message message) {}\nDafür zwei Gründe; die Ankunftsreihenfolge ist nur der dritte. Erstens muss der beobachtende Thread für jedes abonnierte Verzeichnis ansprechbar bleiben: ein Callback, der transformiert, veröffentlicht oder blockiert, hielte die Beobachtung aller anderen auf. Zweitens reist der Postfachname mit der Nachricht, sodass eine Schleife im Dienst deren Bedeutung bestimmen kann — Steuerpostfach, also ein anzuwendender Intent; abonnierte Quelle, also zu transformierende Daten — und dieselbe Schleife darf Abonnements hinzufügen oder entfernen, weil sie nicht in einem Callback feststeckt.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-two-publications",
|
||||
"href": "05-part-v-subscriptions.html#sec-two-publications",
|
||||
"title": "6 Teil V — Die dynamische Idee über Prozesse hinweg wiederholen",
|
||||
"section": "6.3 Zwei Veröffentlichungen statt vier",
|
||||
"text": "6.3 Zwei Veröffentlichungen statt vier\nStarten Sie SensorService, DynamicProcessorService und DynamicActuatorService — ohne Vermittler — und lassen Sie dann Configure.java die zwei TOPIC-Nachrichten veröffentlichen. Eine danach getippte Zeile hinterlässt genau zwei Anwendungsveröffentlichungen im Brett:\n\n\n\n\n\n\n\n\nPostfach\nInhalt\nwas es ist\n\n\n\n\nconsoleIn/outbox\nTEXT hello\ndie Eingabe\n\n\nrot13/outbox\nTEXT uryyb\ndas Ergebnis\n\n\nrot13/inbox\nTOPIC consoleIn/outbox\nIntent, einmal veröffentlicht\n\n\nconsoleOut/inbox\nTOPIC rot13/outbox\nIntent, einmal veröffentlicht\n\n\n\nconsoleOut/inbox enthält keine Nutzlast: ConsoleOut nimmt direkt aus rot13/outbox. Sein Postfach wechselte die Aufgabe, von Nachrichten zu Verdrahtung.\nEine Zeile, die vor dem Lauf von Configure.java getippt wurde, bleibt für immer in consoleIn/outbox. Ein Abonnement, das noch nicht existiert, verpasst, was ihm vorausging — dieselbe Lehre wie beim neu gestarteten Vermittler, der nichts auslieferte.\n\n\n\nFassung\nAnwendungsveröffentlichungen\nProzesse im Datenpfad\n\n\n\n\nvermittelt (Schritt 18)\n4\n5\n\n\nkonfigurierbarer Vermittler (Schritt 27)\n4\n5\n\n\ndynamisch (Schritt 38)\n2\n3",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html",
|
||||
"href": "06-part-vi-vocabulary.html",
|
||||
"title": "7 Teil VI — Über Syncthing wiederholen und die Nachrichten benennen",
|
||||
"section": "",
|
||||
"text": "7.1 Der verteilte dynamische Lauf\nDie Schritte 39 bis 47 verteilen die dynamische Fassung auf zwei Maschinen, sagen genau, was „direkt” bedeutet, und geben dann — erst jetzt, nachdem die Ideen benutzt wurden — den drei Nachrichtenarten ihre Namen: Intent, Status, Event.\nSensor auf einer Maschine, ROT13 und der Aktor auf der anderen, nirgends ein Vermittler. Nachdem die zwei TOPIC-Intents repliziert waren, erzeugte eine getippte Zeile das Ergebnis auf der anderen Maschine — und das Brett zeigt die Kosten:\nSpannend war die Zeit. Die Eingabe wurde um 02:35:12 veröffentlicht, die Ergebnisse erschienen auf der ersten Maschine um 04:11:28,797 und ,893 — 96 ms auseinander, lange nach der Eingabe. Syncthing war über Nacht überlastet; der Stapel kam, als die Warteschlange abfloss. Die Kette war durchgehend korrekt; die Latenz des Transports steuert die Architektur nicht. Zum Vergleich: 24 ms für dieselbe Kette auf einer Maschine.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-distributed-dynamic",
|
||||
"href": "06-part-vi-vocabulary.html#sec-distributed-dynamic",
|
||||
"title": "7 Teil VI — Über Syncthing wiederholen und die Nachrichten benennen",
|
||||
"section": "",
|
||||
"text": "consoleIn/outbox: die Eingabe;\nrot13/outbox: das Ergebnis, geschrieben von dem Dienst, der es erzeugt hat;\nconsoleOut/inbox: nur Intent, wo die vermittelte Fassung eine vollständige Kopie jeder Nachricht hielt.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-direct-precisely",
|
||||
"href": "06-part-vi-vocabulary.html#sec-direct-precisely",
|
||||
"title": "7 Teil VI — Über Syncthing wiederholen und die Nachrichten benennen",
|
||||
"section": "7.2 Was „direkt” genau bedeutet",
|
||||
"text": "7.2 Was „direkt” genau bedeutet\nZwei Sprünge, die gleich aussehen, sind architektonisch Gegensätze:\n\nein Transportsprung — Syncthing auf jeder Seite, möglicherweise ein Relay dazwischen — fügt keinen Beteiligten hinzu, der die Topologie kennt, und nichts reagiert darauf. Liefen die Pakete über einen anderen Kontinent, widerspräche das keiner Aussage hier.\nein architektonischer Sprung — ein Vermittler, der consoleIn/outbox → rot13/inbox kopiert — fügt eine Komponente hinzu, die beide Namen kennen muss, in der Verfügbarkeitskette steht und die Nachricht erneut veröffentlicht.\n\nDie vertretbare Aussage lautet daher: ROT13 reagiert auf ConsoleIns Veröffentlichung, ohne eine unserer Komponenten dazwischen und ohne ConsoleIns Identität zu enthalten. Nicht: die Daten gehen direkt von A nach B. Die Architektur bestimmt, auf welche Nachrichten ein Dienst reagiert, nicht die Wegewahl des Transports.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-ise",
|
||||
"href": "06-part-vi-vocabulary.html#sec-ise",
|
||||
"title": "7 Teil VI — Über Syncthing wiederholen und die Nachrichten benennen",
|
||||
"section": "7.3 Intent, Status, Event",
|
||||
"text": "7.3 Intent, Status, Event\nDrei Nachrichtenarten, benannt erst nach ihrem Gebrauch:\n\n\n\n\n\n\n\n\n\nsagt\nunsere Beispiele\n\n\n\n\nE — Event\netwas ist geschehen\nTEXT hello als ConsoleIn/E/text; TEXT uryyb als ROT13/E/crypted\n\n\nS — Status/State\netwas ist gerade wahr\nROT13/S/subscriptions — von unserem System noch nicht veröffentlicht\n\n\nI — Intent\nwas geschehen soll\nTOPIC consoleIn/outbox, ROUTE … …\n\n\n\nVergangenheitsform ist ein nützlicher Hinweis für Events. Für Intent lautet der Test zwei Fragen: berichtet die Nachricht etwas Geschehenes? Nein. Etwas gerade Wahres? Nein. Dann verlangt sie Verhalten.\nEine Falle: einen Intent zu veröffentlichen ist natürlich etwas Geschehenes. Eingeordnet wird nach dem, was die Nachricht sagt, nicht nach ihrer Existenz — sonst wird alles zum Event und das Vokabular nützt nichts mehr.\nStatus verdient eine eigene Anmerkung, denn der Instinkt ist, ihn zu erfragen: „welche Abonnements hast du?” Doch Fragen ist ein Aufruf, und ein Aufruf verlangt, dass der Fragende die Komponente kennt, sie als laufend weiss und wartet. Status wird veröffentlicht: ROT13 veröffentlicht ROT13/S/subscriptions, sobald sich seine Verdrahtung ändert, und wer will, liest es. Der Leser braucht dann ein Topic, keine Komponente, und ROT13 erfährt nie, wer es prüft. Jede Art beantwortet eine andere Frage:\n\nein Event nützt nur, wenn man zuhörte — unsere liegengebliebenen Nachrichten, dreimal;\nein Status ist, was ein Neuankömmling braucht: der aktuelle Wert, ohne Geschichte nachzuspielen;\nein Intent verlangt eine Änderung.\n\nUnd Kommandos sind nicht verboten. ROT13/I mit ACTION Hello zu senden ist kommandoartig, und das Urteil des Materials lautet „Fine.” Die Komponente übt ihre Fähigkeit aus und veröffentlicht ihre Events und ihren Status. Der empfohlene Fluss ist Intent → Komponente → State + Events.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-one-writer",
|
||||
"href": "06-part-vi-vocabulary.html#sec-one-writer",
|
||||
"title": "7 Teil VI — Über Syncthing wiederholen und die Nachrichten benennen",
|
||||
"section": "7.4 Die Ein-Schreiber-Regel",
|
||||
"text": "7.4 Die Ein-Schreiber-Regel\n\nJede schreibbare Ressource hat genau eine Schreibautorität.\n\nNicht zu verwechseln mit der UUID im Dateinamen. Die UUID verhindert, dass zwei Veröffentlichungen denselben physischen Namen wählen; die Schreibautorität sagt, welche Komponente eine logische Event- oder Status-Ressource besitzt. Zwei Schreiber kollidieren nie bei einem Dateinamen — genau deshalb wird das Problem leicht übersehen.\nWas ein zweiter Schreiber kostet: der Postfachname war der einzige Herkunftsnachweis, also bedeutet rot13/outbox nicht mehr „ROT13 hat dies transformiert”, und ein Abonnent kann dem Vertrag nicht mehr trauen, auf dem er aufbaut. Für Status ist es schlimmer — zwei Komponenten, die je den aktuellen Wert eines Faktes zu veröffentlichen behaupten, widersprechen sich, ohne Reihenfolgegarantie zwischen Maschinen, die entscheiden könnte. Bei append-only Events koexistieren viele Veröffentlichungen absichtlich; die Frage ist semantischer Besitz, nicht Kollision. Treten zwei Autoritäten auf, frage nach dem Warum, statt zum Lock zu greifen.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html",
|
||||
"href": "07-part-vii-mediation.html",
|
||||
"title": "8 Teil VII — Die zwei architektonischen Ideen zusammenführen",
|
||||
"section": "",
|
||||
"text": "8.1 Ein Transformator verdient seine Existenz\nZwei Vermittler wurden entfernt und der Gewinn gemessen. Die Schritte 48 bis 52 beantworten die naheliegende nächste Frage: ist Vermittlung damit falsch? Nein — und die entscheidende Unterscheidung ist scharf genug, um sie auf einen fremden Entwurf anzuwenden.\nEntfernt wurde ein Vermittler, der A → A berechnete: eine teure Identitätsfunktion in der Verfügbarkeitskette, die jede Nachricht ohne Bedeutungsgewinn kopierte.\nNun ein Produzent, der {\"value\":\"Hello\"} veröffentlicht, und ein Konsument, der eine Anzeigestruktur erwartet. Ein TextToDisplayTransformer dazwischen leistet Schematransformation, semantische Anpassung, möglicherweise Einheitenumrechnung, möglicherweise Aggregation. Das ist Arbeit, die keine der beiden Seiten besitzen sollte: ROT13 hat nicht über Terminalfarben zu entscheiden, und die Konsole hat die Nutzlastform von ROT13 nicht zu verstehen.\nDie Grenze zieht die Vertragskompatibilität, nicht die Frage, ob etwas hinzukommt. Ein Vermittler, der Celsius in Fahrenheit umrechnet, ändert statt hinzuzufügen und hat seinen Platz verdient; einer, der einer schon verstandenen Nachricht einen Zeitstempel anhängt, hat etwas hinzugefügt und bleibt verdächtig. Die Frage ist immer: könnte der Konsument die Nachricht des Produzenten so lesen, wie sie ist?",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-transformer",
|
||||
"href": "07-part-vii-mediation.html#sec-transformer",
|
||||
"title": "8 Teil VII — Die zwei architektonischen Ideen zusammenführen",
|
||||
"section": "",
|
||||
"text": "Versteht ein Konsument die Veröffentlichung eines Produzenten semantisch, genügt direktes Abonnieren oft. Sind die Verträge inkompatibel, führe einen Transformator ein, der eine echte Anpassung leistet.\nEin Vermittler, der nur kompatible Daten weiterleitet, ist verdächtig. Ein Vermittler, der nötige Semantik hinzufügt, hat seine Existenz verdient.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-egoistic-transformer",
|
||||
"href": "07-part-vii-mediation.html#sec-egoistic-transformer",
|
||||
"title": "8 Teil VII — Die zwei architektonischen Ideen zusammenführen",
|
||||
"section": "8.2 Auch der Transformator ist egoistisch",
|
||||
"text": "8.2 Auch der Transformator ist egoistisch\nIn die Kette eingefügt, abonniert der Transformator rot13/outbox und veröffentlicht in sein eigenes Ausgangspostfach; ConsoleOut abonniert dann dieses statt das von ROT13. Was das an Code kostet: nichts. ConsoleOut erhält einen anderen Intent — TOPIC display/outbox statt TOPIC rot13/outbox — und die Kette ist umverdrahtet. ROT13 erfährt nie, dass der Transformator existiert; der Transformator nie, dass ConsoleOut existiert.\nWarum nicht direkt in consoleOut/inbox veröffentlichen und ein Postfach sparen? Vier Gründe:\n\nWissen — er enthielte ConsoleOuts Namen, also Topologie in einem Dienst, der Rückfall von Schritt 28;\nBesitz — dieses Postfach ist ConsoleOuts Steuerkanal, geschrieben vom Konfigurator; Nutzlast vom Transformator gäbe ihm zwei Autoritäten;\nReichweite — sein eigenes Ausgangspostfach kann ein Logger, eine Webansicht oder ein zweites Display kostenlos lesen, während ein Eingangspostfach genau einen Konsumenten bedient;\nVeränderbarkeit — ein Aggregator lässt sich danach durch einen anderen Intent einfügen, ohne eine Komponente zu ändern.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-complete-filesystem",
|
||||
"href": "07-part-vii-mediation.html#sec-complete-filesystem",
|
||||
"title": "8 Teil VII — Die zwei architektonischen Ideen zusammenführen",
|
||||
"section": "8.3 Die vollständige Dateisystem-Architektur",
|
||||
"text": "8.3 Die vollständige Dateisystem-Architektur\nJedes Postfach mit genau einem Schreiber:\n\n\n\n\n\n\n\nPostfach\neinziger Schreiber\n\n\n\n\nconsoleIn/outbox\nSensorService\n\n\nrot13/outbox\nProcessorService\n\n\ndisplay/outbox\nder Transformator\n\n\njedes Steuerpostfach\nder Konfigurator — die eine bestimmte Intent-Autorität\n\n\ndas Terminal\nActuatorService, der kein Postfach schreibt\n\n\n\nEgoistische Fähigkeiten, Intent aus einer Autorität, ein Transformator nur dort, wo Verträge sich unterscheiden, ein Schreiber pro Ressource, und die Topologie nirgends in den Fähigkeiten. Das ist der Entwurf, den das Dateisystem gut genug war zu lehren — und der nächste Teil fragt, wofür das Dateisystem selbst nicht mehr gut genug ist.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html",
|
||||
"href": "08-part-ix-mqtt.html",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "",
|
||||
"text": "9.1 Was das Dateisystem gelehrt hat und wofür es nicht taugt\nDas Dateisystem lehrte Veröffentlichungsgrenzen, Verzeichnisse als Adressen, Beobachtung, unabhängige Prozesse, unabhängige Sprachen, Synchronisationslatenz, Verdrahtung zur Laufzeit, State, Intent, Events, Vermittlerkosten, Dienstbesitz und Transformatordienste. Es war ein guter Lehrer und ist kein eleganter Nachrichten-Broker: am Ende war die Architektur sauber und der Transport ein Haufen .tmp-Dateien, atomarer Verschiebungen, erneuter Scans, geteilter Pfade und Replikationsverzögerung.\nDie Schlussfolgerung ist nicht „Dateien schlecht, MQTT gut”. Das Dateisystem hat einen Vorteil, den MQTT nicht erreicht — es speichert routinemässig Gigabytes bis Terabytes, während Broker und Clients für kleine Nachrichten gebaut sind, und das Stückeln einer riesigen Nutzlast über MQTT heisst, ein Dateitransferprotokoll in einem Nachrichtenprotokoll zu erfinden. Also:\nEin repliziertes Dateisystem gibt zudem jeder Maschine eine lokale Kopie, eine echte Stärke — doch Replikation ist kein Backup: Löschungen und Beschädigungen replizieren mit, sofern nicht eine Versionierung ältere Kopien bewahrt.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-filesystem-verdict",
|
||||
"href": "08-part-ix-mqtt.html#sec-filesystem-verdict",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "",
|
||||
"text": "Nachrichten für Koordination und Ereignisse. Für grosse Daten ein passender Datei- oder Objektspeicher. Eine Nachricht kann Ort, Identität und Metadaten dieser Daten tragen statt der Terabytes selbst.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-mqtt-mapping",
|
||||
"href": "08-part-ix-mqtt.html#sec-mqtt-mapping",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "9.2 MQTT sollte vertraut wirken",
|
||||
"text": "9.2 MQTT sollte vertraut wirken\n\n\n\nDateisystem / Syncthing\nMQTT\n\n\n\n\nWurzel des synchronisierten Nachrichtenbretts\nBroker / Namensraum\n\n\nVerzeichnispfad\nTopic\n\n\n.msg-Datei\nVeröffentlichung\n\n\nDateiinhalt\nNutzlast\n\n\nWatchService\nAbonnement\n\n\ndynamisches Verzeichnis\nTopic / Filter\n\n\nSteuerverzeichnis\nI\n\n\nZustandsverzeichnis\nS/…\n\n\nEreignisverzeichnis\nE/…\n\n\n\nDie gewünschte Reaktion des Materials: „Ach. Diese Architektur kennen wir schon.” MQTT ist ein Transportwechsel, keine architektonische Aussage.\nZwei Dinge, die ein Verzeichnis nicht konnte, in einer Minute auf der Kommandozeile sichtbar. Eine Veröffentlichung vor der Existenz eines Abonnenten erreicht ihn nie — die Lehre der liegengebliebenen Nachrichten zum dritten Mal, nun mit einer Antwort, die das Dateisystem nie hatte. Und ein Filter wie test/# passt auf test/a und test/a/b/c, nicht aber auf testing/x, weil # auf Ebenen arbeitet, nicht auf Zeichenpräfixen; test/+ passte nur eine Ebene tief.\nDie tiefere Korrektur: ein Topic ist kein Behälter. Es gibt kein Objekt namens test/a auf dem Broker. Ein Topic ist ein Routing-Schlüssel, den jede Veröffentlichung trägt und der gegen die Filter derjenigen geprüft wird, die in diesem Moment abonniert haben. Verzeichnisse halten Nachrichten; Topics vergleichen sie. Ein Abonnement deckt daher Topics ab, die noch nicht existieren — wo ein Nachrichtenbrett ein neues Verzeichnis und eine neue Registrierung brauchte.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-paho",
|
||||
"href": "08-part-ix-mqtt.html#sec-paho",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "9.3 Die Bibliothek, die Client-ID und die Broker-Adresse",
|
||||
"text": "9.3 Die Bibliothek, die Client-ID und die Broker-Adresse\nJava hat keinen MQTT-Client in der Standardbibliothek, also kommt Paho jetzt — nach dem Bedarf, wie der Vermittler in Schritt 7 und Jackson in Schritt 64. Vier Dinge braucht man: verbinden, veröffentlichen, abonnieren, Rückruf. Das Verbinden ist absichtlich unspektakulär: „Hier ist architektonisch nichts geschehen. Wir haben unseren Prozess nur an den Transport angeschlossen.”\nZwei Details des Verbindens haben Gewicht:\n\ndie Client-ID ist nicht bloss ein Eindeutigkeitsmerkmal. Der Broker erkennt daran einen zurückkehrenden Client und hält Sitzungszustand für ihn: Abonnements, bei QoS > 0 eingereihte Nachrichten und die Verknüpfung mit seinem Last Will. Ein Verzeichnis wusste nie, wer es beobachtete — genau deshalb spielte ein neu gestarteter Beobachter nichts nach.\ndie Broker-Adresse ist Deployment-Konfiguration: jedes Programm liest System.getProperty(\"mqtt.broker\", \"tcp://localhost:1883\"). Sie ist auch die einzige Konfiguration, die nicht als Intent kommen kann, denn Intent reist durch den Broker. Topologie lässt sich veröffentlichen; die Adresse des Veröffentlichenden nicht.\n\nAbonnieren kostet ein Paket, und der Broker führt die Abonnementliste. Es gibt keinen Standardweg, ihn zu fragen, was ein anderer Client abonniert hat — daher S/subscriptions: die eigene Erklärung einer Komponente über ihre Verdrahtung, veröffentlicht, damit die Architektur weiss, was der Transport privat hält. Nur ihr Eigentümer darf sie veröffentlichen, nach der Ein-Schreiber-Regel, denn nur er weiss, was er angenommen hat.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-structured-intent",
|
||||
"href": "08-part-ix-mqtt.html#sec-structured-intent",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "9.4 Strukturierter Intent und zwei Mapper",
|
||||
"text": "9.4 Strukturierter Intent und zwei Mapper\nTOPIC some/path hat ein Feld und eine Bedeutung. Es kann nicht sagen, welche Art Intent vorliegt, keinen zweiten Parameter tragen, nicht verschachteln, nicht erweitert werden; und ein Empfänger hat nichts, wogegen er prüfen könnte. Reicherer Intent braucht Struktur:\nsubscribe:\n topic: Demo/ConsoleIn/U/alice/E/text\nErst dann hat eine Serialisierungsbibliothek eine klare Aufgabe. JsonTools hält zwei Mapper, und die Asymmetrie ist Absicht:\n\ndas Lesen nutzt eine YAML-Factory mit abgeschaltetem FAIL_ON_UNKNOWN_PROPERTIES — JSON ist eine Teilmenge von YAML, handgetippter Intent wird akzeptiert, und ein neuerer Konfigurator darf Felder senden, die ein älterer Dienst ignoriert;\ndas Schreiben nutzt strenges JSON mit INDENT_OUTPUT, die veröffentlichten Nutzlasten sind also streng und lesbar.\n\nTolerant hinein, streng hinaus. Ein einziger Mapper müsste auf eines davon verzichten.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-duise",
|
||||
"href": "08-part-ix-mqtt.html#sec-duise",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "9.5 DUISE und das Umverdrahten im Betrieb",
|
||||
"text": "9.5 DUISE und das Umverdrahten im Betrieb\nDas Namensschema erhält endlich seinen Namen: Description (welche Verträge dieser Dienst versteht und veröffentlicht), Unit (welche Instanz), Intent (gewünschtes Verhalten), Status (was jetzt gilt), Event (was geschehen ist).\nDemo/ROT13/U/alice/{I, S/online, S/subscriptions/text, E/crypted}\nU/<unit> brauchte das Dateisystem nie: jede Maschine hatte ihr eigenes Replikat desselben relativen Pfades, Instanzidentität war implizit. MQTT hat einen gemeinsamen Namensraum, ein Topic muss also sagen, welche Kopie. U/alice in einer Fähigkeit festzuschreiben ist daher schlimmer, als consoleIn.outbox es je war: es bindet das Build an ein Deployment. Per Intent konfiguriert, dient ein Build allen — daher die drei Unit-Namen als Argumente von MqttConfigure. Die Unit-Namen sind die Topologie.\nUmverdrahten, am laufenden System beobachtet: einen neuen Intent mit anderer Quelle veröffentlichen, und der Dienst kündigt die alte, abonniert die neue und veröffentlicht S/subscriptions passend neu. Kein Neustart, keine Änderung. Schickt man stattdessen einen ungültigen Filter — Demo/#/E/text, wo # nicht die letzte Ebene ist — weist MqttTools.isValidFilter ihn ab; das alte Abonnement bleibt, und der Status sagt weiter die Wahrheit.\nDiese Abweisung legt eine echte Lücke offen, die man benennen und nicht verstecken sollte: sie wird nur lokal protokolliert. Der Konfigurator erfährt nicht, ob sein Intent angewandt oder abgelehnt wurde, und ein Monitor kann „abgelehnt” nicht von „noch nicht verarbeitet” unterscheiden. In diesem Entwurf erfährt ein Sender das Ergebnis, indem er den Status liest und mit seiner Anfrage vergleicht. Abweisungen als Event zu veröffentlichen oder ein Letzter-Fehler-Status würden die Lücke schliessen; beides steht nicht im Material — es ist eine zu begründende Entwurfsentscheidung.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-retained-and-will",
|
||||
"href": "08-part-ix-mqtt.html#sec-retained-and-will",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "9.6 Was ein neuer Abonnent erfährt und was ein Toter zugibt",
|
||||
"text": "9.6 Was ein neuer Abonnent erfährt und was ein Toter zugibt\nDrei Sekunden Demo/# abonnieren, ohne dass etwas veröffentlicht wird, ergibt dies:\nDemo/ROT13/U/nitro5/S/online {\"value\":true}\nDemo/ROT13/U/nitro5/S/subscriptions/text \"Demo/ConsoleIn/U/nitro5/E/text\"\nDemo/ConsoleOut/U/nitro5/S/online {\"value\":true}\nDemo/ConsoleOut/U/nitro5/S/subscriptions/text \"Demo/ROT13/U/nitro5/E/crypted\"\nEin Spätankömmling erfährt augenblicklich die gesamte aktuelle Verdrahtung des Systems, ohne jemanden zu fragen und ohne dass eine Komponente von einem Monitor weiss. Das ist retained Status. Keine Events kommen an, denn Events werden nicht retained veröffentlicht — „retained State, nicht retained Events”. Es ist auch die richtige Antwort auf den Reflex, einen Dienst zu fragen, was er tut: niemand fragt; der Dienst erklärt es einmal, und der Broker bewahrt es für jeden, der kommt.\nRetained Status allein würde allerdings lügen. Beendet man einen Dienst mit Ctrl+C, bleibt sein S/online = true für immer beim Broker. Daher der Last Will, bei der Verbindung registriert:\nvar will = new MqttMessage(\"{\\\"value\\\":false}\".getBytes(UTF_8), 1, true, new MqttProperties());\noptions.setWill(lastWillTopic, will);\nDer Will ist retained, ersetzt also beim Veröffentlichen durch den Broker das veraltete true. Die Komponente, die ausfällt, ist nicht die, die den Ausfall meldet — die einzige Anordnung, die funktionieren kann. Ein Vorbehalt: ein sauberes DISCONNECT löst keinen Will aus; ein gut erzogener Dienst veröffentlicht daher beim Beenden selbst online=false, und der Will deckt die hässlichen Tode.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-coupling-remains",
|
||||
"href": "08-part-ix-mqtt.html#sec-coupling-remains",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "9.7 Was den Transport überlebte und welche Kopplung bleibt",
|
||||
"text": "9.7 Was den Transport überlebte und welche Kopplung bleibt\nDie untere Hälfte der Tabelle Dateisystem→MQTT ist der Punkt: I, S, E, egoistische Dienste, Topologie zur Laufzeit und „Transformator wenn nötig” sind unverändert. Die Architektur überlebte den Transportwechsel, und das ist der stärkste verfügbare Beleg, dass sie nie am Transport hing.\nLose Kopplung heisst nicht, dass nichts etwas weiss. Notwendig bleibt die Einigkeit über: Nachrichtensyntax, Nachrichtensemantik, Topic-Verträge, Intent, Besitz, Bedeutung von State und Bedeutung von Events. Ziel ist nicht, Kopplung zu beseitigen, sondern unnötiges Wissen zu beseitigen. Konkret muss hier jeder Dienst genau einen fremden Event-Vertrag verstehen — ROT13 den E/text von ConsoleIn, ConsoleOut den E/crypted von ROT13 — plus das Intent-Schema, das er auf seinem eigenen I annimmt. Diese Liste ist das unverzichtbare Minimum.\nDavon getrennt: der Broker ist eine geteilte Infrastrukturabhängigkeit; alle brauchen seine Adresse, und ohne ihn läuft nichts. Real, aber anderer Art als das Wissen einer Komponente über eine andere.\nDie Prüfliste aus Schritt 78 ist das Werkzeug, das bleibt. Zwölf Fragen, von denen diese sechs das Argument dieses Systems tragen:\n\n\n\n\n\n\n\nFrage\nAntwort hier\n\n\n\n\nenthält eine Fähigkeit eine festgeschriebene Produzentenidentität?\nnein — sie kommt als Intent\n\n\nwelche fremden Verträge muss sie verstehen?\nje einen Event-Vertrag, plus ihr eigenes Intent-Schema\n\n\nwo ist die Topologie definiert?\nim Konfigurator, ausserhalb des Datenpfads\n\n\nkann sich die Topologie ohne Neukompilieren ändern?\nja — am laufenden System gezeigt\n\n\nkönnte der Transport ersetzt werden?\nja — gezeigt: Dateisystem, dann MQTT\n\n\nleistet jeder Vermittler etwas, das Vermittlung braucht?\nja, trivial: TEXT → TEXT braucht keine, und es gibt keinen\n\n\n\nDie Mahnung des Materials gilt: die Antworten müssen nicht alle „nein” lauten. Sie müssen absichtlich sein.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-whole-journey",
|
||||
"href": "08-part-ix-mqtt.html#sec-whole-journey",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "9.8 Der ganze Weg",
|
||||
"text": "9.8 Der ganze Weg\nDas Programm hat sich nie geändert: eine Zeile geht hinein, dieselbe kommt um 13 Buchstaben verschoben heraus. Geändert hat sich, elfmal, wie die Teile verbunden sind und wer das Wissen über diese Verbindung hält.\n\n\n\n\n\n\n\n\n\nStufe\nwie die Teile verbunden sind\nwo die Topologie liegt\nim Datenpfad ausser den Fähigkeiten\n\n\n\n\n1 prozedural\ndirekte Aufrufe\nim Code der Fähigkeit\n—\n\n\n2 egoistische Dienste\ngar nicht verbunden\nnirgends — das ist das Problem\n—\n\n\n3 statische Vermittlung, eine JVM\nPostfächer, von Vermittlern kopiert\ndie Vermittler, gestartet in main()\nzwei Vermittler\n\n\n4 statische Vermittlung, Dateisystem\nVerzeichnisse, von Vermittlerprozessen kopiert\ndie Befehlszeilen des Bedieners\nzwei Vermittlerprozesse\n\n\n5 statische Vermittlung, Syncthing\nreplizierte Verzeichnisse\ndie Befehlszeilen des Bedieners\nzwei Vermittlerprozesse, dazu Replikationsverzögerung\n\n\n6 benannte, konfigurierbare Vermittler\nROUTE-Intent von einem Orchestrator\nder Orchestrator, ausserhalb des Pfads\nweiterhin die Vermittler\n\n\n7 dynamisch, eine JVM\ndie Dienste hören selbst, gesteuert durch TOPIC-Intent\nder Konfigurator\nnichts\n\n\n8 dynamisch, Dateisystem\ndasselbe, über Verzeichnisse\nder Konfigurator\nnichts\n\n\n9 dynamisch, Syncthing\ndasselbe, über replizierte Verzeichnisse\nder Konfigurator\nnichts — nur Transportsprünge\n\n\n10 Verträge\nkompatibel: direkt; inkompatibel: ein Transformator\nder Konfigurator\nein Transformator, nur wo Verträge sich unterscheiden\n\n\n11 MQTT\nTopics auf einem Broker\nder Konfigurator\nnichts — der Broker ist Transport\n\n\n\nDie dritte Spalte von oben nach unten gelesen: die Topologie wandert nach aussen, Stufe um Stufe, bis keine Fähigkeit mehr etwas davon hält. Die letzte gelesen: der Preis dieser Wanderung fällt in Stufe 7 auf null und bleibt dort, während darunter dreimal der Transport wechselt. Dieselbe Architektur, besserer Transport.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-sentences",
|
||||
"href": "08-part-ix-mqtt.html#sec-sentences",
|
||||
"title": "9 Teil IX — MQTT",
|
||||
"section": "9.9 Die Sätze, die man behalten sollte",
|
||||
"text": "9.9 Die Sätze, die man behalten sollte\n\n„Event-driven” beschreibt, wie Information und Steuerung fliessen.\nLose Kopplung beschreibt, wie viel die Beteiligten voneinander wissen müssen.\nVeröffentliche, was geschehen ist.\nErkläre, was du willst.\nVeröffentliche deinen eigenen Zustand.\nHalte Fähigkeiten egoistisch.\nHalte die Topologie aus den Fähigkeiten heraus.\nBezahle keinen Vermittler, der nicht wirklich vermittelt.\n\nUnd wann immer eine Architektur verwirrend wird, zurück zur ersten Frage dieses Buches: wer kennt wen?",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "glossary.html",
|
||||
"href": "glossary.html",
|
||||
|
||||
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
@@ -1,126 +0,0 @@
|
||||
// quiz — judge the tick boxes of one quiz, explain what went wrong
|
||||
//
|
||||
// Every label the reader sees is written into the markup by quiz.lua, so the
|
||||
// wording follows the book's language and nothing is translated twice. A
|
||||
// quiz carries:
|
||||
// data-quiz-score "{n} of {m} questions correct" ({n}/{m} substituted)
|
||||
// data-quiz-right verdict of a question answered correctly
|
||||
// data-quiz-wrong verdict of a question answered wrongly
|
||||
//
|
||||
// A question is right only when every one of its options is in the right
|
||||
// state: ticked when true, left empty when false. That is the "multiple
|
||||
// true/false" rule of the exam, and it is why a half-ticked question counts
|
||||
// as wrong.
|
||||
(function () {
|
||||
"use strict";
|
||||
|
||||
function options(quiz) {
|
||||
return quiz.querySelectorAll(".quiz-opt");
|
||||
}
|
||||
|
||||
function judge(quiz) {
|
||||
var questions = quiz.querySelectorAll(".quiz-q");
|
||||
var right = 0;
|
||||
|
||||
questions.forEach(function (q) {
|
||||
var ok = true;
|
||||
|
||||
q.querySelectorAll(".quiz-opt").forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (!box) return;
|
||||
var want = opt.dataset.correct === "1";
|
||||
var hit = box.checked === want;
|
||||
|
||||
opt.classList.toggle("quiz-ok", hit);
|
||||
opt.classList.toggle("quiz-bad", !hit);
|
||||
|
||||
// the explanation of an option is for the reader who got it wrong
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = hit;
|
||||
|
||||
if (!hit) ok = false;
|
||||
});
|
||||
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) {
|
||||
verdict.hidden = false;
|
||||
verdict.textContent = ok
|
||||
? (quiz.dataset.quizRight || "Correct")
|
||||
: (quiz.dataset.quizWrong || "Not quite");
|
||||
verdict.classList.toggle("quiz-ok", ok);
|
||||
verdict.classList.toggle("quiz-bad", !ok);
|
||||
}
|
||||
|
||||
// a question-level explanation backs up a wrong answer as a whole
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = ok;
|
||||
|
||||
if (ok) right++;
|
||||
});
|
||||
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) {
|
||||
var template = quiz.dataset.quizScore || "{n}/{m}";
|
||||
score.innerHTML = "";
|
||||
// built as nodes, not markup: the template comes from metadata
|
||||
var parts = template.split(/\{n\}|\{m\}/);
|
||||
var values = [];
|
||||
(template.match(/\{n\}|\{m\}/g) || []).forEach(function (token) {
|
||||
values.push(token === "{n}" ? right : questions.length);
|
||||
});
|
||||
parts.forEach(function (text, i) {
|
||||
score.appendChild(document.createTextNode(text));
|
||||
if (i < values.length) {
|
||||
var b = document.createElement("b");
|
||||
b.textContent = String(values[i]);
|
||||
score.appendChild(b);
|
||||
}
|
||||
});
|
||||
}
|
||||
}
|
||||
|
||||
function reset(quiz) {
|
||||
options(quiz).forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (box) box.checked = false;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-verdict").forEach(function (v) {
|
||||
v.hidden = true;
|
||||
v.textContent = "";
|
||||
v.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-why-q").forEach(function (w) { w.hidden = true; });
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) score.textContent = "";
|
||||
}
|
||||
|
||||
document.addEventListener("click", function (event) {
|
||||
var target = event.target;
|
||||
if (!target.closest) return;
|
||||
|
||||
var check = target.closest(".quiz .quiz-check");
|
||||
if (check) {
|
||||
judge(check.closest(".quiz"));
|
||||
return;
|
||||
}
|
||||
var again = target.closest(".quiz .quiz-reset");
|
||||
if (again) {
|
||||
reset(again.closest(".quiz"));
|
||||
}
|
||||
});
|
||||
|
||||
// re-ticking a box after checking clears that row's verdict, so a stale
|
||||
// green or red never sits next to a box the reader has just changed
|
||||
document.addEventListener("change", function (event) {
|
||||
var box = event.target;
|
||||
if (!box.closest || !box.classList || !box.classList.contains("quiz-box")) return;
|
||||
var opt = box.closest(".quiz-opt");
|
||||
if (!opt) return;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
})();
|
||||
+40
@@ -113,6 +113,31 @@
|
||||
margin-top: 0.5rem;
|
||||
}
|
||||
|
||||
/* ---- the per-question points badge ---------------------------------- */
|
||||
|
||||
/* The head now always exists (it is where the badge lands), so an empty one
|
||||
on a single-question quiz must not leave a gap. */
|
||||
.quiz-q-head:empty { display: none; }
|
||||
|
||||
.quiz-q-head {
|
||||
display: flex;
|
||||
align-items: baseline;
|
||||
justify-content: space-between;
|
||||
gap: 0.6rem;
|
||||
}
|
||||
|
||||
.quiz-q-score {
|
||||
font-size: 0.82rem;
|
||||
font-weight: 400;
|
||||
color: var(--quiz-ink);
|
||||
white-space: nowrap;
|
||||
}
|
||||
.quiz-q-score b { color: var(--calc-notecolor, #B45309); font-weight: 600; }
|
||||
/* green and red stay reserved for a judged answer; the badge follows the
|
||||
verdict right below it so the two never disagree */
|
||||
.quiz-q-score.quiz-ok b { color: var(--quiz-ok); }
|
||||
.quiz-q-score.quiz-bad b { color: var(--quiz-bad); }
|
||||
|
||||
/* ---- verdict and bar ------------------------------------------------ */
|
||||
|
||||
.quiz-verdict {
|
||||
@@ -160,6 +185,18 @@
|
||||
|
||||
/* ---- dark theme ----------------------------------------------------- */
|
||||
|
||||
/* High contrast remaps the whole palette, and --quiz-ok / --quiz-bad are local
|
||||
to this file, so they have to be pointed at the HC pair by hand: without
|
||||
this the verdict and the points badge keep their ordinary-mode green and
|
||||
red, which is exactly what a reader turns HC on to avoid. `body` makes it
|
||||
outweigh body.quarto-dark .quiz below, or dark + HC would keep the plain
|
||||
dark pair. */
|
||||
html.hc body .quiz {
|
||||
--quiz-ok: var(--hc-success);
|
||||
--quiz-bad: var(--hc-danger);
|
||||
--quiz-ink: var(--hc-fg);
|
||||
}
|
||||
|
||||
body.quarto-dark .quiz {
|
||||
--quiz-ok: #4cb08a;
|
||||
--quiz-bad: #e2798f;
|
||||
@@ -174,5 +211,8 @@ body.quarto-dark .quiz {
|
||||
*/
|
||||
@media print {
|
||||
.quiz-bar { display: none; }
|
||||
/* on paper the points are printed in the statement by quiz.lua, so the
|
||||
screen badge would say the same thing twice */
|
||||
.quiz-q-score { display: none; }
|
||||
.quiz-opt.quiz-ok, .quiz-opt.quiz-bad { background: none; }
|
||||
}
|
||||
@@ -0,0 +1,183 @@
|
||||
// quiz — judge the tick boxes of one quiz, score it in points, explain mistakes
|
||||
//
|
||||
// Every label the reader sees is written into the markup by quiz.lua, so the
|
||||
// wording follows the book's language and nothing is translated twice. A
|
||||
// quiz carries:
|
||||
// data-quiz-score "{n} of {m} questions correct"
|
||||
// data-quiz-points "{n} of {m} points" (the headline)
|
||||
// data-quiz-qpoints "{n}/{m} points" (one question's badge)
|
||||
// data-quiz-right verdict of a question answered correctly
|
||||
// data-quiz-wrong verdict of a question answered wrongly
|
||||
// and each question carries data-points / data-penalty.
|
||||
//
|
||||
// SCORING. A question is worth data-points (default 3). Every statement whose
|
||||
// box disagrees with its truth value — an unticked true one, or a ticked false
|
||||
// one — costs data-penalty (default 1). The result floors at zero, so a
|
||||
// question can never drag the total down. The quiz total is the sum over its
|
||||
// questions. A question still counts as "correct" for the verdict line only
|
||||
// when every one of its statements is right, which is the exam's
|
||||
// multiple-true-false rule.
|
||||
(function () {
|
||||
"use strict";
|
||||
|
||||
function options(quiz) {
|
||||
return quiz.querySelectorAll(".quiz-opt");
|
||||
}
|
||||
|
||||
// Number(undefined) || 3 would also swallow a deliberate 0, so test first.
|
||||
function num(el, name, dflt) {
|
||||
var raw = el.dataset ? el.dataset[name] : null;
|
||||
if (raw === undefined || raw === null || raw === "") return dflt;
|
||||
var n = Number(raw);
|
||||
return isFinite(n) ? n : dflt;
|
||||
}
|
||||
|
||||
// Substitute {n} and {m} into a template from metadata, building text nodes
|
||||
// rather than markup: the template is author text, never trusted as HTML.
|
||||
function render(el, template, n, m) {
|
||||
el.innerHTML = "";
|
||||
var parts = template.split(/\{n\}|\{m\}/);
|
||||
var values = (template.match(/\{n\}|\{m\}/g) || []).map(function (token) {
|
||||
return token === "{n}" ? n : m;
|
||||
});
|
||||
parts.forEach(function (text, i) {
|
||||
el.appendChild(document.createTextNode(text));
|
||||
if (i < values.length) {
|
||||
var b = document.createElement("b");
|
||||
b.textContent = String(values[i]);
|
||||
el.appendChild(b);
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
function judge(quiz) {
|
||||
var questions = quiz.querySelectorAll(".quiz-q");
|
||||
var right = 0, scored = 0, available = 0;
|
||||
|
||||
questions.forEach(function (q) {
|
||||
var ok = true;
|
||||
var misses = 0;
|
||||
var pts = num(q, "points", 3);
|
||||
var pen = num(q, "penalty", 1);
|
||||
|
||||
q.querySelectorAll(".quiz-opt").forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (!box) return;
|
||||
var want = opt.dataset.correct === "1";
|
||||
var hit = box.checked === want;
|
||||
|
||||
opt.classList.toggle("quiz-ok", hit);
|
||||
opt.classList.toggle("quiz-bad", !hit);
|
||||
|
||||
// the explanation of an option is for the reader who got it wrong.
|
||||
// :scope > keeps this to the option's own .why — a question-level
|
||||
// .quiz-why-q also carries the class quiz-why.
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = hit;
|
||||
|
||||
if (!hit) { ok = false; misses++; }
|
||||
});
|
||||
|
||||
var got = Math.max(0, pts - misses * pen);
|
||||
scored += got;
|
||||
available += pts;
|
||||
|
||||
var badge = q.querySelector(".quiz-q-score");
|
||||
if (badge) {
|
||||
badge.hidden = false;
|
||||
render(badge, quiz.dataset.quizQpoints || "{n}/{m}", got, pts);
|
||||
badge.classList.toggle("quiz-ok", misses === 0);
|
||||
badge.classList.toggle("quiz-bad", got === 0 && pts > 0);
|
||||
}
|
||||
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) {
|
||||
verdict.hidden = false;
|
||||
verdict.textContent = ok
|
||||
? (quiz.dataset.quizRight || "Correct")
|
||||
: (quiz.dataset.quizWrong || "Not quite");
|
||||
verdict.classList.toggle("quiz-ok", ok);
|
||||
verdict.classList.toggle("quiz-bad", !ok);
|
||||
}
|
||||
|
||||
// a question-level explanation backs up a wrong answer as a whole
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = ok;
|
||||
|
||||
if (ok) right++;
|
||||
});
|
||||
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) {
|
||||
score.hidden = false;
|
||||
render(score, quiz.dataset.quizPoints || "{n}/{m}", scored, available);
|
||||
}
|
||||
}
|
||||
|
||||
function reset(quiz) {
|
||||
options(quiz).forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (box) box.checked = false;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-verdict").forEach(function (v) {
|
||||
v.hidden = true;
|
||||
v.textContent = "";
|
||||
v.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-q-score").forEach(function (b) {
|
||||
b.hidden = true;
|
||||
b.textContent = "";
|
||||
b.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-why-q").forEach(function (w) { w.hidden = true; });
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) { score.textContent = ""; score.hidden = false; }
|
||||
}
|
||||
|
||||
document.addEventListener("click", function (event) {
|
||||
var target = event.target;
|
||||
if (!target.closest) return;
|
||||
|
||||
var check = target.closest(".quiz .quiz-check");
|
||||
if (check) {
|
||||
judge(check.closest(".quiz"));
|
||||
return;
|
||||
}
|
||||
var again = target.closest(".quiz .quiz-reset");
|
||||
if (again) {
|
||||
reset(again.closest(".quiz"));
|
||||
}
|
||||
});
|
||||
|
||||
// Re-ticking a box after checking clears that row's verdict, so a stale
|
||||
// green or red never sits next to a box the reader has just changed — and
|
||||
// with it the question's badge and the headline, which would otherwise
|
||||
// still claim a score for an answer that has since moved.
|
||||
document.addEventListener("change", function (event) {
|
||||
var box = event.target;
|
||||
if (!box.closest || !box.classList || !box.classList.contains("quiz-box")) return;
|
||||
var opt = box.closest(".quiz-opt");
|
||||
if (!opt) return;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
|
||||
var q = opt.closest(".quiz-q");
|
||||
if (q) {
|
||||
var badge = q.querySelector(".quiz-q-score");
|
||||
if (badge) { badge.hidden = true; badge.textContent = ""; }
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) { verdict.hidden = true; verdict.textContent = ""; }
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = true;
|
||||
}
|
||||
var quiz = opt.closest(".quiz");
|
||||
if (quiz) {
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) score.textContent = "";
|
||||
}
|
||||
});
|
||||
})();
|
||||
@@ -52,19 +52,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -510,6 +510,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Partie IV — Rembobinage</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Partie V — Rejouer l’idée dynamique entre processus</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Partie VI — Rejouer sur Syncthing, et nommer les messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Partie VII — Fusionner les deux idées architecturales</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Partie IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Partie IV — Rembobinage</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Partie V — Rejouer l’idée dynamique entre processus</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Partie VI — Rejouer sur Syncthing, et nommer les messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Partie VII — Fusionner les deux idées architecturales</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Partie IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Partie IV — Rembobinage</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Partie V — Rejouer l’idée dynamique entre processus</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Partie VI — Rejouer sur Syncthing, et nommer les messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Partie VII — Fusionner les deux idées architecturales</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Partie IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -52,19 +52,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -510,6 +510,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Partie IV — Rembobinage</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Partie V — Rejouer l’idée dynamique entre processus</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Partie VI — Rejouer sur Syncthing, et nommer les messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Partie VII — Fusionner les deux idées architecturales</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Partie IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
|
||||
@@ -71,7 +71,7 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<script src="site_libs/quarto-search/fuse.min.js"></script>
|
||||
<script src="site_libs/quarto-search/quarto-search.js"></script>
|
||||
<meta name="quarto:offset" content="./">
|
||||
<link href="./glossary.html" rel="next">
|
||||
<link href="./05-part-v-subscriptions.html" rel="next">
|
||||
<link href="./03-part-iii-distributed.html" rel="prev">
|
||||
<script src="site_libs/quarto-html/quarto.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/tabsets/tabsets.js" type="module"></script>
|
||||
@@ -87,19 +87,19 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -545,6 +545,30 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link active">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Partie IV — Rembobinage</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Partie V — Rejouer l’idée dynamique entre processus</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Partie VI — Rejouer sur Syncthing, et nommer les messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Partie VII — Fusionner les deux idées architecturales</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Partie IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -604,7 +628,7 @@ pre > code.sourceCode > span > a:first-child::before { text-decoration: underlin
|
||||
|
||||
|
||||
<!-- MULTILINGUAL: see the comment at the top of index.qmd. -->
|
||||
<p>Les étapes 28 à 34 reviennent volontairement à une seule JVM. Sans délai de réplication ni cinq terminaux, la seule chose qui peut changer est qui connaît qui — l’idée s’essaie donc en quelques secondes plutôt qu’au cours d’une séance de débogage distribué.</p>
|
||||
<p>Les étapes 28 à 34 reviennent volontairement à une seule JVM. Sans délai de réplication ni cinq terminaux, la seule chose qui peut changer est qui connaît qui — l’idée s’essaie donc en quelques secondes plutôt que pendant une séance de débogage distribué.</p>
|
||||
<section id="sec-the-trap" class="level2" data-number="5.1">
|
||||
<h2 data-number="5.1" class="anchored" data-anchor-id="sec-the-trap"><span class="header-section-number">5.1</span> Le raccourci évident, et son piège</h2>
|
||||
<p>Si le premier médiateur ne fait que copier des messages, supprimons-le et laissons ROT13 lire la source lui-même :</p>
|
||||
@@ -1281,8 +1305,8 @@ Producteur → Médiateur → Consommateur Intent → (Producteur ──► Co
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-page nav-page-next">
|
||||
<a href="./glossary.html" class="pagination-link" aria-label="[Glossary]{.en}[Glossaire]{.fr}[Glossar]{.de}">
|
||||
<span class="nav-page-text">Glossaire</span> <i class="bi bi-arrow-right-short"></i>
|
||||
<a href="./05-part-v-subscriptions.html" class="pagination-link" aria-label="[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}">
|
||||
<span class="nav-page-text"><span class="chapter-number">6</span> <span class="chapter-title">Partie V — Rejouer l’idée dynamique entre processus</span></span> <i class="bi bi-arrow-right-short"></i>
|
||||
</a>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
File diff suppressed because it is too large.
Load diff
Binary file not shown.
+40
-16
@@ -36,7 +36,7 @@ ul.task-list li input[type="checkbox"] {
|
||||
<script src="site_libs/quarto-search/fuse.min.js"></script>
|
||||
<script src="site_libs/quarto-search/quarto-search.js"></script>
|
||||
<meta name="quarto:offset" content="./">
|
||||
<link href="./04-part-iv-rewind.html" rel="prev">
|
||||
<link href="./08-part-ix-mqtt.html" rel="prev">
|
||||
<script src="site_libs/quarto-html/quarto.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/tabsets/tabsets.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/popper.min.js"></script>
|
||||
@@ -51,19 +51,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -509,6 +509,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Partie IV — Rembobinage</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Partie V — Rejouer l’idée dynamique entre processus</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Partie VI — Rejouer sur Syncthing, et nommer les messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Partie VII — Fusionner les deux idées architecturales</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Partie IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -1211,8 +1235,8 @@ Every entry here is defined in the chapter where the term first does some
|
||||
</script>
|
||||
<nav class="page-navigation">
|
||||
<div class="nav-page nav-page-previous">
|
||||
<a href="./04-part-iv-rewind.html" class="pagination-link" aria-label="[Part IV — Rewind]{.en}[Partie IV — Rembobinage]{.fr}[Teil IV — Zurückspulen]{.de}">
|
||||
<i class="bi bi-arrow-left-short"></i> <span class="nav-page-text"><span class="chapter-number">5</span> <span class="chapter-title">Partie IV — Rembobinage</span></span>
|
||||
<a href="./08-part-ix-mqtt.html" class="pagination-link" aria-label="[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}">
|
||||
<i class="bi bi-arrow-left-short"></i> <span class="nav-page-text"><span class="chapter-number">9</span> <span class="chapter-title">Partie IX — MQTT</span></span>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-page nav-page-next">
|
||||
|
||||
+38
-14
@@ -52,19 +52,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -510,6 +510,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Partie IV — Rembobinage</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Partie V — Rejouer l’idée dynamique entre processus</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Partie VI — Rejouer sur Syncthing, et nommer les messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Partie VII — Fusionner les deux idées architecturales</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Partie IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -568,7 +592,7 @@ ul.task-list li input[type="checkbox"] {
|
||||
<div>
|
||||
<div class="quarto-title-meta-heading">Date de publication</div>
|
||||
<div class="quarto-title-meta-contents">
|
||||
<p class="date">6 octobre 2026</p>
|
||||
<p class="date">16 octobre 2026</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
+231
-1
@@ -284,7 +284,7 @@
|
||||
"href": "04-part-iv-rewind.html",
|
||||
"title": "5 Partie IV — Rembobinage",
|
||||
"section": "",
|
||||
"text": "5.1 Le raccourci évident, et son piège\nLes étapes 28 à 34 reviennent volontairement à une seule JVM. Sans délai de réplication ni cinq terminaux, la seule chose qui peut changer est qui connaît qui — l’idée s’essaie donc en quelques secondes plutôt qu’au cours d’une séance de débogage distribué.\nSi le premier médiateur ne fait que copier des messages, supprimons-le et laissons ROT13 lire la source lui-même :\nLe médiateur a disparu. Mais posons la question récurrente : ROT13 contient désormais le nom de la boîte de ConsoleIn. La topologie a quitté le médiateur pour entrer dans le service. Comme le dit le matériel : « nous avons supprimé le médiateur… et remis la topologie dans le service. Oups. »",
|
||||
"text": "5.1 Le raccourci évident, et son piège\nLes étapes 28 à 34 reviennent volontairement à une seule JVM. Sans délai de réplication ni cinq terminaux, la seule chose qui peut changer est qui connaît qui — l’idée s’essaie donc en quelques secondes plutôt que pendant une séance de débogage distribué.\nSi le premier médiateur ne fait que copier des messages, supprimons-le et laissons ROT13 lire la source lui-même :\nLe médiateur a disparu. Mais posons la question récurrente : ROT13 contient désormais le nom de la boîte de ConsoleIn. La topologie a quitté le médiateur pour entrer dans le service. Comme le dit le matériel : « nous avons supprimé le médiateur… et remis la topologie dans le service. Oups. »",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>5</span> <span class='chapter-title'>[Part IV — Rewind]{.en}[Partie IV — Rembobinage]{.fr}[Teil IV — Zurückspulen]{.de}</span>"
|
||||
]
|
||||
@@ -329,6 +329,236 @@
|
||||
"<span class='chapter-number'>5</span> <span class='chapter-title'>[Part IV — Rewind]{.en}[Partie IV — Rembobinage]{.fr}[Teil IV — Zurückspulen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html",
|
||||
"href": "05-part-v-subscriptions.html",
|
||||
"title": "6 Partie V — Rejouer l’idée dynamique entre processus",
|
||||
"section": "",
|
||||
"text": "6.1 Une observation bloquante ne suffit pas\nLes étapes 35 à 38 sortent l’idée d’abonnement de la JVM unique. Les services redeviennent des programmes séparés, mais au lieu de médiateurs qui copient des fichiers, chaque service observe la boîte qu’on lui a indiquée. Une hypothèse du premier utilitaire de fichiers ne survit pas au déplacement, et c’est bien de la corriger qu’il s’agit ici.\nFileMessageBoard.watch(topic, receiver) enregistre un répertoire et se bloque indéfiniment. Cela suffisait tant que chaque processus observait une boîte fixe. Un service câblé dynamiquement demande davantage :\nL’ancienne signature ne peut pas exprimer cela, et la conséquence était déjà visible : le médiateur configurable n’acceptait qu’une seule ROUTE, car dès qu’il observait sa source il devenait sourd à sa propre boîte de contrôle. La limite n’a jamais été de qui est le répertoire, mais un seul, fixe, pour toujours.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-watch-limit",
|
||||
"href": "05-part-v-subscriptions.html#sec-watch-limit",
|
||||
"title": "6 Partie V — Rejouer l’idée dynamique entre processus",
|
||||
"section": "",
|
||||
"text": "observer en permanence sa propre boîte de contrôle\nET\najouter un répertoire observé à l'exécution\nET\néventuellement le retirer ensuite",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-filesubscriptions",
|
||||
"href": "05-part-v-subscriptions.html#sec-filesubscriptions",
|
||||
"title": "6 Partie V — Rejouer l’idée dynamique entre processus",
|
||||
"section": "6.2 L’utilitaire : FileSubscriptions",
|
||||
"text": "6.2 L’utilitaire : FileSubscriptions\nUn seul WatchService peut servir plusieurs répertoires. register(...) retourne un WatchKey qui en identifie un, watcher.take() retourne la clé qui a des événements, et key.cancel() la désenregistre. L’utilitaire garde les deux sens, nom → clé et clé → nom, pour qu’un événement puisse être rattaché à la boîte dont il vient.\nLes événements n’arrivent pas directement dans un callback. Ils passent par une file, lue avec take(), et portent\nrecord IncomingMessage(String mailbox, Message message) {}\nDeux raisons, l’ordre d’arrivée n’étant que la troisième. D’abord, le thread observateur doit rester réactif pour tous les répertoires abonnés : un callback qui transforme, publie ou bloque arrêterait l’observation de tous les autres. Ensuite, le nom de la boîte voyage avec le message, de sorte qu’une seule boucle du service peut décider de son sens — boîte de contrôle, donc un Intent à appliquer ; source abonnée, donc des données à transformer — et cette même boucle peut ajouter ou retirer des abonnements, puisqu’elle n’est pas prisonnière d’un callback.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-two-publications",
|
||||
"href": "05-part-v-subscriptions.html#sec-two-publications",
|
||||
"title": "6 Partie V — Rejouer l’idée dynamique entre processus",
|
||||
"section": "6.3 Deux publications au lieu de quatre",
|
||||
"text": "6.3 Deux publications au lieu de quatre\nLancez SensorService, DynamicProcessorService et DynamicActuatorService — sans médiateurs — puis laissez Configure.java publier les deux messages TOPIC. Une ligne tapée ensuite laisse exactement deux publications applicatives dans le tableau :\n\n\n\nboîte\ncontenu\nnature\n\n\n\n\nconsoleIn/outbox\nTEXT hello\nl’entrée\n\n\nrot13/outbox\nTEXT uryyb\nle résultat\n\n\nrot13/inbox\nTOPIC consoleIn/outbox\nIntent, publié une fois\n\n\nconsoleOut/inbox\nTOPIC rot13/outbox\nIntent, publié une fois\n\n\n\nconsoleOut/inbox ne contient aucune charge utile : ConsoleOut retire directement de rot13/outbox. Sa boîte a changé de métier, des messages vers le câblage.\nUne ligne tapée avant l’exécution de Configure.java reste dans consoleIn/outbox pour toujours. Un abonnement qui n’existe pas encore manque ce qui l’a précédé — le même constat que le médiateur redémarré qui n’a rien livré.\n\n\n\n\n\n\n\n\nversion\npublications applicatives\nprocessus dans le chemin des données\n\n\n\n\nmédiée (étape 18)\n4\n5\n\n\nmédiateur configurable (étape 27)\n4\n5\n\n\ndynamique (étape 38)\n2\n3",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html",
|
||||
"href": "06-part-vi-vocabulary.html",
|
||||
"title": "7 Partie VI — Rejouer sur Syncthing, et nommer les messages",
|
||||
"section": "",
|
||||
"text": "7.1 L’exécution dynamique distribuée\nLes étapes 39 à 47 répartissent la version dynamique sur deux machines, précisent ce que « direct » veut dire, puis — maintenant seulement, après avoir utilisé les idées — donnent leurs noms aux trois sortes de messages : Intent, Status, Event.\nCapteur sur une machine, ROT13 et l’actionneur sur l’autre, aucun médiateur. Après la réplication des deux Intents TOPIC, une ligne tapée a produit le résultat sur l’autre machine — et le tableau montre ce que cela coûte :\nLe temps est la partie intéressante. L’entrée a été publiée à 02:35:12 et les résultats sont apparus sur la première machine à 04:11:28,797 et ,893 — à 96 ms d’écart, bien après l’entrée. Syncthing était saturé pendant la nuit : le lot est arrivé quand la file s’est vidée. La chaîne est restée correcte ; la latence du transport n’est tout simplement pas contrôlée par l’architecture. À comparer aux 24 ms de la même chaîne sur une seule machine.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-distributed-dynamic",
|
||||
"href": "06-part-vi-vocabulary.html#sec-distributed-dynamic",
|
||||
"title": "7 Partie VI — Rejouer sur Syncthing, et nommer les messages",
|
||||
"section": "",
|
||||
"text": "consoleIn/outbox : l’entrée ;\nrot13/outbox : le résultat, écrit par le service qui l’a produit ;\nconsoleOut/inbox : de l’Intent seulement, là où la version médiée contenait une copie complète de chaque message.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-direct-precisely",
|
||||
"href": "06-part-vi-vocabulary.html#sec-direct-precisely",
|
||||
"title": "7 Partie VI — Rejouer sur Syncthing, et nommer les messages",
|
||||
"section": "7.2 Ce que « direct » veut dire, exactement",
|
||||
"text": "7.2 Ce que « direct » veut dire, exactement\nDeux sauts qui se ressemblent sont architecturalement opposés :\n\nun saut de transport — Syncthing de chaque côté, éventuellement un relais entre les deux — n’ajoute aucun participant qui connaisse la topologie, et rien n’y réagit. Si les paquets passaient par un autre continent, aucune affirmation ici ne serait contredite.\nun saut architectural — un médiateur copiant consoleIn/outbox → rot13/inbox — ajoute un composant qui doit connaître les deux noms, se place dans la chaîne de disponibilité et republie le message.\n\nL’affirmation défendable est donc : ROT13 réagit à la publication de ConsoleIn sans aucun de nos composants entre les deux, et sans contenir l’identité de ConsoleIn. Et non : les données vont directement de A à B. L’architecture décide à quels messages un service réagit, pas du routage du transport.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-ise",
|
||||
"href": "06-part-vi-vocabulary.html#sec-ise",
|
||||
"title": "7 Partie VI — Rejouer sur Syncthing, et nommer les messages",
|
||||
"section": "7.3 Intent, Status, Event",
|
||||
"text": "7.3 Intent, Status, Event\nTrois sortes de messages, nommées seulement après avoir été utilisées :\n\n\n\n\n\n\n\n\n\ndit\nnos exemples\n\n\n\n\nE — Event\nquelque chose est arrivé\nTEXT hello comme ConsoleIn/E/text ; TEXT uryyb comme ROT13/E/crypted\n\n\nS — Status/State\nquelque chose est actuellement vrai\nROT13/S/subscriptions — pas encore publié par notre système\n\n\nI — Intent\nce qui devrait arriver\nTOPIC consoleIn/outbox, ROUTE … …\n\n\n\nLe passé composé est un bon indice pour les Events. Pour l’Intent, le test tient en deux questions : le message rapporte-t-il quelque chose qui est arrivé ? Non. Quelque chose d’actuellement vrai ? Non. Alors il demande un comportement.\nUn piège : publier un Intent est bien sûr quelque chose qui est arrivé. Il faut classer d’après ce que dit le message, non d’après son existence — sinon tout devient Event et le vocabulaire ne sert plus à rien.\nLe Status mérite une note, car l’instinct est de le demander : « quels sont tes abonnements ? » Mais demander, c’est appeler, et un appel exige que le demandeur connaisse le composant, le sache en vie, et attende. Le Status se publie : ROT13 publie ROT13/S/subscriptions dès que son câblage change, et quiconque s’y intéresse le lit. Le lecteur a alors besoin d’un sujet, pas d’un composant, et ROT13 n’apprend jamais qui l’audite. Chaque sorte répond à une question différente :\n\nun Event n’est utile que si l’on écoutait — nos messages bloqués, trois fois de suite ;\nun Status est ce dont un nouveau venu a besoin : la valeur actuelle, sans rejouer l’histoire ;\nun Intent demande un changement.\n\nEt les commandes ne sont pas interdites. Envoyer ROT13/I avec ACTION Hello ressemble à une commande, et le verdict du matériel est « Fine. » Le composant exerce sa capacité et publie ses Events et son Status. Le flux retenu est Intent → composant → State + Events.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-one-writer",
|
||||
"href": "06-part-vi-vocabulary.html#sec-one-writer",
|
||||
"title": "7 Partie VI — Rejouer sur Syncthing, et nommer les messages",
|
||||
"section": "7.4 La règle de l’écrivain unique",
|
||||
"text": "7.4 La règle de l’écrivain unique\n\nToute ressource écrivable a exactement une autorité d’écriture.\n\nNe pas confondre avec l’UUID du nom de fichier. L’UUID empêche deux publications de choisir le même nom physique ; l’autorité d’écriture dit quel composant possède une ressource logique d’Event ou de Status. Deux écrivains n’entrent jamais en collision sur un nom de fichier, et c’est précisément pour cela que le problème passe inaperçu.\nCe que coûte un second écrivain : le nom de la boîte était le seul marqueur de provenance, donc rot13/outbox cesse de signifier « ROT13 a transformé ceci » et un abonné ne peut plus faire confiance au contrat sur lequel il s’appuie. Pour le Status c’est pire — deux composants prétendant chacun publier la valeur actuelle d’un même fait se contredisent, sans aucune garantie d’ordre entre machines pour trancher. Pour des Events en ajout seul, de nombreuses publications coexistent par construction ; la question est la propriété sémantique, pas la collision. Quand deux autorités apparaissent, demandez pourquoi il y en a deux plutôt que de sortir un verrou.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html",
|
||||
"href": "07-part-vii-mediation.html",
|
||||
"title": "8 Partie VII — Fusionner les deux idées architecturales",
|
||||
"section": "",
|
||||
"text": "8.1 Un transformateur mérite d’exister\nDeux médiateurs ont été supprimés et le gain mesuré. Les étapes 48 à 52 répondent à la question suivante, évidente : la médiation est-elle pour autant mauvaise ? Non — et la distinction qui tranche est assez nette pour s’appliquer à une conception qu’on n’a jamais vue.\nCe qui a été supprimé, c’est un médiateur calculant A → A : une fonction identité coûteuse, dans la chaîne de disponibilité, copiant chaque message sans rien y ajouter.\nPrenons maintenant un producteur publiant {\"value\":\"Hello\"} et un consommateur attendant une structure d’affichage. Un TextToDisplayTransformer entre les deux apporte transformation de schéma, adaptation sémantique, éventuellement conversion d’unités, éventuellement agrégation. C’est un travail qu’aucun des deux ne devrait porter : ROT13 n’a pas à décider des couleurs du terminal, et la console n’a pas à comprendre la forme de la charge utile de ROT13.\nLa ligne se trace par la compatibilité des contrats, non par le fait d’ajouter quelque chose. Un médiateur convertissant des Celsius en Fahrenheit modifie au lieu d’ajouter et mérite sa place ; un médiateur ajoutant un horodatage à un message que le consommateur comprend déjà a ajouté quelque chose et reste suspect. La question est toujours : le consommateur pourrait-il lire le message du producteur tel quel ?",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-transformer",
|
||||
"href": "07-part-vii-mediation.html#sec-transformer",
|
||||
"title": "8 Partie VII — Fusionner les deux idées architecturales",
|
||||
"section": "",
|
||||
"text": "Si un consommateur comprend sémantiquement la publication d’un producteur, l’abonnement direct suffit souvent. Si les contrats sont incompatibles, introduire un transformateur qui effectue une adaptation réelle.\nUn médiateur qui ne fait que transmettre des données compatibles est suspect. Un médiateur qui ajoute la sémantique nécessaire mérite d’exister.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-egoistic-transformer",
|
||||
"href": "07-part-vii-mediation.html#sec-egoistic-transformer",
|
||||
"title": "8 Partie VII — Fusionner les deux idées architecturales",
|
||||
"section": "8.2 Le transformateur est égoïste aussi",
|
||||
"text": "8.2 Le transformateur est égoïste aussi\nInséré dans la chaîne, le transformateur s’abonne à rot13/outbox et publie dans sa propre boîte de sortie ; ConsoleOut s’abonne alors à celle du transformateur plutôt qu’à celle de ROT13. Notez ce que cela coûte en code : rien. ConsoleOut reçoit un autre Intent — TOPIC display/outbox au lieu de TOPIC rot13/outbox — et la chaîne est recâblée. ROT13 n’apprend jamais que le transformateur existe ; le transformateur n’apprend jamais que ConsoleOut existe.\nPourquoi ne pas publier directement dans consoleOut/inbox, en économisant une boîte ? Quatre raisons :\n\nconnaissance — il contiendrait le nom de ConsoleOut, c’est-à-dire de la topologie dans un service, la rechute de l’étape 28 ;\npropriété — cette boîte est le canal de contrôle de ConsoleOut, écrit par le configurateur ; une charge utile venue du transformateur lui donnerait deux autorités ;\nportée — sa propre boîte peut être lue par un journal, une vue web ou un second affichage sans frais, alors qu’une boîte d’entrée ne sert qu’un consommateur ;\nmutabilité — un agrégateur peut être inséré ensuite en envoyant un autre Intent, sans modifier aucun composant.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-complete-filesystem",
|
||||
"href": "07-part-vii-mediation.html#sec-complete-filesystem",
|
||||
"title": "8 Partie VII — Fusionner les deux idées architecturales",
|
||||
"section": "8.3 L’architecture complète sur système de fichiers",
|
||||
"text": "8.3 L’architecture complète sur système de fichiers\nChaque boîte avec exactement un écrivain :\n\n\n\n\n\n\n\nboîte\nécrivain unique\n\n\n\n\nconsoleIn/outbox\nSensorService\n\n\nrot13/outbox\nProcessorService\n\n\ndisplay/outbox\nle transformateur\n\n\nchaque boîte de contrôle\nle configurateur — l’unique autorité d’Intent désignée\n\n\nle terminal\nActuatorService, qui n’écrit aucune boîte\n\n\n\nDes capacités égoïstes, l’Intent venant d’une seule autorité, un transformateur seulement là où les contrats diffèrent, un écrivain par ressource, et la topologie nulle part dans les capacités. C’est la conception que le système de fichiers a suffi à enseigner — et la partie suivante demande à quoi le système de fichiers, lui, ne suffit plus.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html",
|
||||
"href": "08-part-ix-mqtt.html",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "",
|
||||
"text": "9.1 Ce que le système de fichiers a enseigné, et ce pour quoi il n’est pas fait\nLe système de fichiers a enseigné les frontières de publication, les répertoires comme adresses, l’observation, des processus indépendants, des langages indépendants, la latence de synchronisation, le câblage à l’exécution, le State, l’Intent, les Events, le coût des médiateurs, la propriété des services et les services transformateurs. Ce fut un bon professeur, et ce n’est pas un courtier de messages élégant : à la fin, l’architecture était propre et le transport était un amas de fichiers .tmp, de déplacements atomiques, de rescans, de chemins partagés et de délais de réplication.\nLa conclusion n’est pas « fichiers mauvais, MQTT bon ». Le système de fichiers a un avantage que MQTT ne peut égaler — il stocke couramment des gigaoctets ou des téraoctets, alors que courtiers et clients sont conçus pour de petits messages, et découper une charge énorme sur MQTT revient à inventer un protocole de transfert de fichiers dans un protocole de messages. Donc :\nUn système de fichiers répliqué donne aussi à chaque machine une copie locale, ce qui est une vraie force — mais la réplication n’est pas une sauvegarde : suppressions et corruptions se répliquent aussi, à moins qu’un versionnement conserve les copies antérieures.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-filesystem-verdict",
|
||||
"href": "08-part-ix-mqtt.html#sec-filesystem-verdict",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "",
|
||||
"text": "Utilisez les messages pour la coordination et les événements. Utilisez un stockage de fichiers ou d’objets adapté pour les grandes données. Un message peut porter l’emplacement, l’identité et les métadonnées de ces données au lieu des téraoctets eux-mêmes.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-mqtt-mapping",
|
||||
"href": "08-part-ix-mqtt.html#sec-mqtt-mapping",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "9.2 MQTT devrait sembler familier",
|
||||
"text": "9.2 MQTT devrait sembler familier\n\n\n\n\n\n\n\nsystème de fichiers / Syncthing\nMQTT\n\n\n\n\nracine du tableau de messages synchronisé\ncourtier / espace de noms\n\n\nchemin de répertoire\nsujet (topic)\n\n\nfichier .msg\npublication\n\n\ncontenu du fichier\ncharge utile\n\n\nWatchService\nabonnement\n\n\nrépertoire dynamique\nsujet / filtre\n\n\nrépertoire de contrôle\nI\n\n\nrépertoire d’état\nS/…\n\n\nrépertoire d’événements\nE/…\n\n\n\nLa réaction visée par le matériel : « Ah. Nous connaissons déjà cette architecture. » MQTT est un changement de transport, pas une affirmation architecturale.\nDeux choses qu’un répertoire ne pouvait pas faire, visibles en une minute en ligne de commande. Une publication faite avant l’existence d’un abonné ne lui parvient jamais — le constat des messages bloqués, pour la troisième fois, mais avec une réponse que le système de fichiers n’avait pas. Et un filtre comme test/# correspond à test/a et test/a/b/c mais pas à testing/x, car # travaille par niveaux et non par préfixes de chaîne ; test/+ ne correspondrait qu’à un seul niveau.\nLa correction plus profonde : un sujet n’est pas un conteneur. Il n’existe aucun objet nommé test/a sur le courtier. Un sujet est une clé de routage portée par chaque publication et confrontée aux filtres de qui est abonné à cet instant. Les répertoires contiennent les messages ; les sujets les filtrent. Un seul abonnement couvre donc des sujets qui n’existent pas encore — là où un tableau de messages exigeait un nouveau répertoire et un nouvel enregistrement.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-paho",
|
||||
"href": "08-part-ix-mqtt.html#sec-paho",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "9.3 La bibliothèque, l’identifiant client et l’adresse du courtier",
|
||||
"text": "9.3 La bibliothèque, l’identifiant client et l’adresse du courtier\nJava n’a pas de client MQTT dans sa bibliothèque standard ; Paho arrive donc maintenant — après le besoin, comme le médiateur à l’étape 7 et Jackson à l’étape 64. Quatre choses suffisent : se connecter, publier, s’abonner, rappeler. La connexion est volontairement anticlimatique : « Rien d’architectural ne s’est produit ici. Nous avons simplement attaché notre processus au transport. »\nDeux détails de la connexion comptent :\n\nl’identifiant client n’est pas qu’un jeton d’unicité. Le courtier reconnaît par lui un client qui revient et conserve son état de session : abonnements, messages en file en QoS > 0, et l’association à sa dernière volonté. Un répertoire ne savait jamais qui l’observait, et c’est précisément pour cela qu’un observateur redémarré ne rejouait rien.\nl’adresse du courtier est de la configuration de déploiement : chaque programme lit System.getProperty(\"mqtt.broker\", \"tcp://localhost:1883\"). C’est aussi la seule configuration qui ne peut pas arriver par Intent, puisque l’Intent passe par le courtier. La topologie se publie ; l’adresse de ce qui la publie, non.\n\nS’abonner coûte un paquet, et le courtier détient la liste des abonnements. Il n’existe aucun moyen standard de lui demander à quoi un autre client s’est abonné — d’où S/subscriptions : la déclaration par un composant de son propre câblage, publiée pour que l’architecture sache ce que le transport garde privé. Seul son propriétaire peut la publier, par la règle de l’écrivain unique, car seul lui sait ce qu’il a accepté.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-structured-intent",
|
||||
"href": "08-part-ix-mqtt.html#sec-structured-intent",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "9.4 Intent structuré, et deux mappeurs",
|
||||
"text": "9.4 Intent structuré, et deux mappeurs\nTOPIC some/path a un champ et un sens. Il ne peut pas dire de quel type d’Intent il s’agit, porter un second paramètre, s’imbriquer ou s’étendre ; et un récepteur n’a rien contre quoi valider. Un Intent plus riche demande une structure :\nsubscribe:\n topic: Demo/ConsoleIn/U/alice/E/text\nC’est seulement là qu’une bibliothèque de sérialisation a une tâche claire. JsonTools garde deux mappeurs, et l’asymétrie est voulue :\n\nen entrée, une fabrique YAML avec FAIL_ON_UNKNOWN_PROPERTIES désactivé — JSON étant un sous-ensemble de YAML, un Intent tapé à la main est accepté, et un configurateur plus récent peut envoyer des champs qu’un service plus ancien ignore ;\nl’écriture utilise du JSON strict avec INDENT_OUTPUT activé, donc les charges publiées sont strictes et lisibles.\n\nTolérant en entrée, strict en sortie. Un mappeur unique devrait renoncer à l’un des deux.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-duise",
|
||||
"href": "08-part-ix-mqtt.html#sec-duise",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "9.5 DUISE, et recâbler un système en marche",
|
||||
"text": "9.5 DUISE, et recâbler un système en marche\nLe schéma de nommage reçoit enfin son nom : Description (quels contrats ce service comprend et publie), Unit (quelle instance), Intent (comportement demandé), Status (ce qui est vrai maintenant), Event (ce qui est arrivé).\nDemo/ROT13/U/alice/{I, S/online, S/subscriptions/text, E/crypted}\nU/<unit> est ce dont le système de fichiers n’avait pas besoin : chaque machine avait sa réplique du même chemin relatif, l’identité d’instance était implicite. MQTT a un espace de noms partagé : un sujet doit donc dire quelle copie. Coder en dur U/alice dans une capacité est donc pire que de coder en dur consoleIn.outbox : cela lie la compilation à un déploiement. Configuré par Intent, une seule compilation sert tout le monde — d’où les trois noms d’unité en arguments de MqttConfigure. Les noms d’unité sont la topologie.\nRecâblage observé sur un système en marche : publiez un nouvel Intent nommant une autre source, et le service se désabonne de l’ancienne, s’abonne à la nouvelle et republie S/subscriptions en conséquence. Sans redémarrage, sans édition. Envoyez au contraire un filtre invalide — Demo/#/E/text, où # n’est pas le dernier niveau — et MqttTools.isValidFilter le rejette ; l’ancien abonnement demeure et le Status continue de dire vrai.\nCe rejet révèle une vraie lacune, à nommer plutôt qu’à cacher : il n’est journalisé que localement. Le configurateur ne peut savoir si son Intent a été appliqué ou refusé, et un moniteur ne peut distinguer « refusé » de « pas encore traité ». Dans cette conception, l’émetteur apprend le résultat en lisant le Status et en le comparant à sa demande. Publier les refus comme Event, ou un Status de dernière erreur, combleraient la lacune ; ni l’un ni l’autre n’est dans le matériel : c’est une décision de conception à justifier.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-retained-and-will",
|
||||
"href": "08-part-ix-mqtt.html#sec-retained-and-will",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "9.6 Ce qu’un nouvel abonné apprend, et ce qu’un mort avoue",
|
||||
"text": "9.6 Ce qu’un nouvel abonné apprend, et ce qu’un mort avoue\nS’abonner à Demo/# pendant trois secondes, sans que rien ne soit publié, renvoie ceci :\nDemo/ROT13/U/nitro5/S/online {\"value\":true}\nDemo/ROT13/U/nitro5/S/subscriptions/text \"Demo/ConsoleIn/U/nitro5/E/text\"\nDemo/ConsoleOut/U/nitro5/S/online {\"value\":true}\nDemo/ConsoleOut/U/nitro5/S/subscriptions/text \"Demo/ROT13/U/nitro5/E/crypted\"\nUn arrivant tardif apprend instantanément tout le câblage actuel du système, sans rien demander et sans qu’aucun composant sache qu’un moniteur existe. C’est le Status retenu. Aucun Event n’arrive, car les Events sont publiés non retenus — « State retenu, Events non retenus ». C’est aussi la bonne réponse à l’instinct de demander à un service ce qu’il fait : personne ne demande ; le service le déclare, une fois, et le courtier le garde pour quiconque se présente.\nLe Status retenu seul mentirait pourtant. Tuez un service par Ctrl+C et son S/online = true reste sur le courtier à jamais. D’où la dernière volonté, enregistrée au moment de la connexion :\nvar will = new MqttMessage(\"{\\\"value\\\":false}\".getBytes(UTF_8), 1, true, new MqttProperties());\noptions.setWill(lastWillTopic, will);\nElle est retenue : quand le courtier la publie au nom du client, elle remplace le true périmé. Le composant qui échoue n’est pas celui qui signale l’échec — seul arrangement qui puisse fonctionner. Une réserve : une déconnexion propre ne déclenche pas la dernière volonté ; un service bien élevé publie donc online=false lui-même en partant, la volonté couvrant les morts brutales.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-coupling-remains",
|
||||
"href": "08-part-ix-mqtt.html#sec-coupling-remains",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "9.7 Ce qui a survécu au transport, et le couplage restant",
|
||||
"text": "9.7 Ce qui a survécu au transport, et le couplage restant\nLa moitié inférieure du tableau système de fichiers→MQTT est l’essentiel : I, S, E, les services égoïstes, la topologie à l’exécution et « transformateur si nécessaire » sont inchangés. L’architecture a survécu au remplacement du transport, et c’est la meilleure preuve disponible qu’elle n’a jamais dépendu du transport.\nUn couplage faible ne signifie pas que rien ne sait rien. Ce qui reste, nécessairement, est l’accord sur : la syntaxe des messages, leur sémantique, les contrats de sujets, l’Intent, la propriété, le sens du State et celui des Events. Le but n’est pas d’éliminer le couplage mais d’éliminer la connaissance inutile. Concrètement, chaque service ici doit comprendre exactement un contrat d’Event étranger — ROT13 comprend E/text de ConsoleIn, ConsoleOut comprend E/crypted de ROT13 — plus le schéma d’Intent qu’il accepte sur son propre I. Cette liste est le minimum irréductible.\nPar ailleurs, le courtier est une dépendance d’infrastructure partagée : tout le monde a besoin de son adresse et rien ne marche sans lui. Réel, mais d’une autre nature que la connaissance d’un composant par un autre.\nLa liste de l’étape 78 est l’outil à garder. Douze questions, dont ces six portent l’argument de ce système :\n\n\n\n\n\n\n\nquestion\nréponse ici\n\n\n\n\nune capacité contient-elle l’identité d’un producteur en dur ?\nnon — elle arrive par Intent\n\n\nquels contrats étrangers doit-elle comprendre ?\nun contrat d’Event chacun, plus son propre schéma d’Intent\n\n\noù la topologie est-elle définie ?\ndans le configurateur, hors du chemin des données\n\n\nla topologie peut-elle changer sans recompiler ?\noui — démontré sur un système en marche\n\n\nle transport pourrait-il être remplacé ?\noui — démontré : système de fichiers puis MQTT\n\n\nchaque médiateur fait-il quelque chose qui exige une médiation ?\noui, trivialement : TEXT → TEXT n’en exige aucune, et il n’y en a aucun\n\n\n\nLa prudence du matériel s’applique : les réponses n’ont pas à être toutes « non ». Elles doivent être intentionnelles.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-whole-journey",
|
||||
"href": "08-part-ix-mqtt.html#sec-whole-journey",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "9.8 Le parcours complet",
|
||||
"text": "9.8 Le parcours complet\nLe programme n’a jamais changé : une ligne entre, la même ressort décalée de 13 lettres. Ce qui a changé, onze fois, c’est la manière dont les parties sont reliées et qui détient la connaissance de ce câblage.\n\n\n\n\n\n\n\n\n\nétape\ncomment les parties sont reliées\noù vit la topologie\ndans le chemin des données, outre les capacités\n\n\n\n\n1 procédural\nappels directs\ndans le code de la capacité\n—\n\n\n2 services égoïstes\npas reliées du tout\nnulle part — c’est le problème\n—\n\n\n3 médiation statique, une JVM\nboîtes, copiées par des médiateurs\nles médiateurs, démarrés dans main()\ndeux médiateurs\n\n\n4 médiation statique, système de fichiers\nrépertoires, copiés par des processus médiateurs\nles lignes de commande de l’opérateur\ndeux processus médiateurs\n\n\n5 médiation statique, Syncthing\nrépertoires répliqués\nles lignes de commande de l’opérateur\ndeux processus médiateurs, plus le délai de réplication\n\n\n6 médiateurs nommés et configurables\nIntent ROUTE d’un orchestrateur\nl’orchestrateur, hors du chemin\nles médiateurs, encore\n\n\n7 dynamique, une JVM\nles services écoutent, guidés par un Intent TOPIC\nle configurateur\nrien\n\n\n8 dynamique, système de fichiers\nidem, sur des répertoires\nle configurateur\nrien\n\n\n9 dynamique, Syncthing\nidem, sur des répertoires répliqués\nle configurateur\nrien — seulement des sauts de transport\n\n\n10 contrats\ncompatibles : direct ; incompatibles : un transformateur\nle configurateur\nun transformateur, seulement là où les contrats diffèrent\n\n\n11 MQTT\ndes sujets sur un courtier\nle configurateur\nrien — le courtier est du transport\n\n\n\nLisez la troisième colonne de haut en bas : la topologie s’éloigne, une étape après l’autre, jusqu’à ce qu’aucune capacité n’en détienne plus rien. Lisez la dernière : le prix de ce déplacement tombe à zéro à l’étape 7 et y reste pendant que le transport change trois fois en dessous. Même architecture, meilleur transport.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-sentences",
|
||||
"href": "08-part-ix-mqtt.html#sec-sentences",
|
||||
"title": "9 Partie IX — MQTT",
|
||||
"section": "9.9 Les phrases à retenir",
|
||||
"text": "9.9 Les phrases à retenir\n\n« Event-driven » décrit comment circulent l’information et le contrôle.\nLe couplage faible décrit ce que les participants doivent savoir les uns des autres.\nPubliez ce qui est arrivé.\nDéclarez ce que vous voulez.\nPubliez votre propre état.\nGardez les capacités égoïstes.\nGardez la topologie hors des capacités.\nNe payez pas un médiateur qui ne fait pas réellement de médiation.\n\nEt chaque fois qu’une architecture devient confuse, revenez à la première question de ce livre : qui connaît qui ?",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "glossary.html",
|
||||
"href": "glossary.html",
|
||||
|
||||
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
@@ -1,126 +0,0 @@
|
||||
// quiz — judge the tick boxes of one quiz, explain what went wrong
|
||||
//
|
||||
// Every label the reader sees is written into the markup by quiz.lua, so the
|
||||
// wording follows the book's language and nothing is translated twice. A
|
||||
// quiz carries:
|
||||
// data-quiz-score "{n} of {m} questions correct" ({n}/{m} substituted)
|
||||
// data-quiz-right verdict of a question answered correctly
|
||||
// data-quiz-wrong verdict of a question answered wrongly
|
||||
//
|
||||
// A question is right only when every one of its options is in the right
|
||||
// state: ticked when true, left empty when false. That is the "multiple
|
||||
// true/false" rule of the exam, and it is why a half-ticked question counts
|
||||
// as wrong.
|
||||
(function () {
|
||||
"use strict";
|
||||
|
||||
function options(quiz) {
|
||||
return quiz.querySelectorAll(".quiz-opt");
|
||||
}
|
||||
|
||||
function judge(quiz) {
|
||||
var questions = quiz.querySelectorAll(".quiz-q");
|
||||
var right = 0;
|
||||
|
||||
questions.forEach(function (q) {
|
||||
var ok = true;
|
||||
|
||||
q.querySelectorAll(".quiz-opt").forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (!box) return;
|
||||
var want = opt.dataset.correct === "1";
|
||||
var hit = box.checked === want;
|
||||
|
||||
opt.classList.toggle("quiz-ok", hit);
|
||||
opt.classList.toggle("quiz-bad", !hit);
|
||||
|
||||
// the explanation of an option is for the reader who got it wrong
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = hit;
|
||||
|
||||
if (!hit) ok = false;
|
||||
});
|
||||
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) {
|
||||
verdict.hidden = false;
|
||||
verdict.textContent = ok
|
||||
? (quiz.dataset.quizRight || "Correct")
|
||||
: (quiz.dataset.quizWrong || "Not quite");
|
||||
verdict.classList.toggle("quiz-ok", ok);
|
||||
verdict.classList.toggle("quiz-bad", !ok);
|
||||
}
|
||||
|
||||
// a question-level explanation backs up a wrong answer as a whole
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = ok;
|
||||
|
||||
if (ok) right++;
|
||||
});
|
||||
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) {
|
||||
var template = quiz.dataset.quizScore || "{n}/{m}";
|
||||
score.innerHTML = "";
|
||||
// built as nodes, not markup: the template comes from metadata
|
||||
var parts = template.split(/\{n\}|\{m\}/);
|
||||
var values = [];
|
||||
(template.match(/\{n\}|\{m\}/g) || []).forEach(function (token) {
|
||||
values.push(token === "{n}" ? right : questions.length);
|
||||
});
|
||||
parts.forEach(function (text, i) {
|
||||
score.appendChild(document.createTextNode(text));
|
||||
if (i < values.length) {
|
||||
var b = document.createElement("b");
|
||||
b.textContent = String(values[i]);
|
||||
score.appendChild(b);
|
||||
}
|
||||
});
|
||||
}
|
||||
}
|
||||
|
||||
function reset(quiz) {
|
||||
options(quiz).forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (box) box.checked = false;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-verdict").forEach(function (v) {
|
||||
v.hidden = true;
|
||||
v.textContent = "";
|
||||
v.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-why-q").forEach(function (w) { w.hidden = true; });
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) score.textContent = "";
|
||||
}
|
||||
|
||||
document.addEventListener("click", function (event) {
|
||||
var target = event.target;
|
||||
if (!target.closest) return;
|
||||
|
||||
var check = target.closest(".quiz .quiz-check");
|
||||
if (check) {
|
||||
judge(check.closest(".quiz"));
|
||||
return;
|
||||
}
|
||||
var again = target.closest(".quiz .quiz-reset");
|
||||
if (again) {
|
||||
reset(again.closest(".quiz"));
|
||||
}
|
||||
});
|
||||
|
||||
// re-ticking a box after checking clears that row's verdict, so a stale
|
||||
// green or red never sits next to a box the reader has just changed
|
||||
document.addEventListener("change", function (event) {
|
||||
var box = event.target;
|
||||
if (!box.closest || !box.classList || !box.classList.contains("quiz-box")) return;
|
||||
var opt = box.closest(".quiz-opt");
|
||||
if (!opt) return;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
})();
|
||||
+40
@@ -113,6 +113,31 @@
|
||||
margin-top: 0.5rem;
|
||||
}
|
||||
|
||||
/* ---- the per-question points badge ---------------------------------- */
|
||||
|
||||
/* The head now always exists (it is where the badge lands), so an empty one
|
||||
on a single-question quiz must not leave a gap. */
|
||||
.quiz-q-head:empty { display: none; }
|
||||
|
||||
.quiz-q-head {
|
||||
display: flex;
|
||||
align-items: baseline;
|
||||
justify-content: space-between;
|
||||
gap: 0.6rem;
|
||||
}
|
||||
|
||||
.quiz-q-score {
|
||||
font-size: 0.82rem;
|
||||
font-weight: 400;
|
||||
color: var(--quiz-ink);
|
||||
white-space: nowrap;
|
||||
}
|
||||
.quiz-q-score b { color: var(--calc-notecolor, #B45309); font-weight: 600; }
|
||||
/* green and red stay reserved for a judged answer; the badge follows the
|
||||
verdict right below it so the two never disagree */
|
||||
.quiz-q-score.quiz-ok b { color: var(--quiz-ok); }
|
||||
.quiz-q-score.quiz-bad b { color: var(--quiz-bad); }
|
||||
|
||||
/* ---- verdict and bar ------------------------------------------------ */
|
||||
|
||||
.quiz-verdict {
|
||||
@@ -160,6 +185,18 @@
|
||||
|
||||
/* ---- dark theme ----------------------------------------------------- */
|
||||
|
||||
/* High contrast remaps the whole palette, and --quiz-ok / --quiz-bad are local
|
||||
to this file, so they have to be pointed at the HC pair by hand: without
|
||||
this the verdict and the points badge keep their ordinary-mode green and
|
||||
red, which is exactly what a reader turns HC on to avoid. `body` makes it
|
||||
outweigh body.quarto-dark .quiz below, or dark + HC would keep the plain
|
||||
dark pair. */
|
||||
html.hc body .quiz {
|
||||
--quiz-ok: var(--hc-success);
|
||||
--quiz-bad: var(--hc-danger);
|
||||
--quiz-ink: var(--hc-fg);
|
||||
}
|
||||
|
||||
body.quarto-dark .quiz {
|
||||
--quiz-ok: #4cb08a;
|
||||
--quiz-bad: #e2798f;
|
||||
@@ -174,5 +211,8 @@ body.quarto-dark .quiz {
|
||||
*/
|
||||
@media print {
|
||||
.quiz-bar { display: none; }
|
||||
/* on paper the points are printed in the statement by quiz.lua, so the
|
||||
screen badge would say the same thing twice */
|
||||
.quiz-q-score { display: none; }
|
||||
.quiz-opt.quiz-ok, .quiz-opt.quiz-bad { background: none; }
|
||||
}
|
||||
@@ -0,0 +1,183 @@
|
||||
// quiz — judge the tick boxes of one quiz, score it in points, explain mistakes
|
||||
//
|
||||
// Every label the reader sees is written into the markup by quiz.lua, so the
|
||||
// wording follows the book's language and nothing is translated twice. A
|
||||
// quiz carries:
|
||||
// data-quiz-score "{n} of {m} questions correct"
|
||||
// data-quiz-points "{n} of {m} points" (the headline)
|
||||
// data-quiz-qpoints "{n}/{m} points" (one question's badge)
|
||||
// data-quiz-right verdict of a question answered correctly
|
||||
// data-quiz-wrong verdict of a question answered wrongly
|
||||
// and each question carries data-points / data-penalty.
|
||||
//
|
||||
// SCORING. A question is worth data-points (default 3). Every statement whose
|
||||
// box disagrees with its truth value — an unticked true one, or a ticked false
|
||||
// one — costs data-penalty (default 1). The result floors at zero, so a
|
||||
// question can never drag the total down. The quiz total is the sum over its
|
||||
// questions. A question still counts as "correct" for the verdict line only
|
||||
// when every one of its statements is right, which is the exam's
|
||||
// multiple-true-false rule.
|
||||
(function () {
|
||||
"use strict";
|
||||
|
||||
function options(quiz) {
|
||||
return quiz.querySelectorAll(".quiz-opt");
|
||||
}
|
||||
|
||||
// Number(undefined) || 3 would also swallow a deliberate 0, so test first.
|
||||
function num(el, name, dflt) {
|
||||
var raw = el.dataset ? el.dataset[name] : null;
|
||||
if (raw === undefined || raw === null || raw === "") return dflt;
|
||||
var n = Number(raw);
|
||||
return isFinite(n) ? n : dflt;
|
||||
}
|
||||
|
||||
// Substitute {n} and {m} into a template from metadata, building text nodes
|
||||
// rather than markup: the template is author text, never trusted as HTML.
|
||||
function render(el, template, n, m) {
|
||||
el.innerHTML = "";
|
||||
var parts = template.split(/\{n\}|\{m\}/);
|
||||
var values = (template.match(/\{n\}|\{m\}/g) || []).map(function (token) {
|
||||
return token === "{n}" ? n : m;
|
||||
});
|
||||
parts.forEach(function (text, i) {
|
||||
el.appendChild(document.createTextNode(text));
|
||||
if (i < values.length) {
|
||||
var b = document.createElement("b");
|
||||
b.textContent = String(values[i]);
|
||||
el.appendChild(b);
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
function judge(quiz) {
|
||||
var questions = quiz.querySelectorAll(".quiz-q");
|
||||
var right = 0, scored = 0, available = 0;
|
||||
|
||||
questions.forEach(function (q) {
|
||||
var ok = true;
|
||||
var misses = 0;
|
||||
var pts = num(q, "points", 3);
|
||||
var pen = num(q, "penalty", 1);
|
||||
|
||||
q.querySelectorAll(".quiz-opt").forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (!box) return;
|
||||
var want = opt.dataset.correct === "1";
|
||||
var hit = box.checked === want;
|
||||
|
||||
opt.classList.toggle("quiz-ok", hit);
|
||||
opt.classList.toggle("quiz-bad", !hit);
|
||||
|
||||
// the explanation of an option is for the reader who got it wrong.
|
||||
// :scope > keeps this to the option's own .why — a question-level
|
||||
// .quiz-why-q also carries the class quiz-why.
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = hit;
|
||||
|
||||
if (!hit) { ok = false; misses++; }
|
||||
});
|
||||
|
||||
var got = Math.max(0, pts - misses * pen);
|
||||
scored += got;
|
||||
available += pts;
|
||||
|
||||
var badge = q.querySelector(".quiz-q-score");
|
||||
if (badge) {
|
||||
badge.hidden = false;
|
||||
render(badge, quiz.dataset.quizQpoints || "{n}/{m}", got, pts);
|
||||
badge.classList.toggle("quiz-ok", misses === 0);
|
||||
badge.classList.toggle("quiz-bad", got === 0 && pts > 0);
|
||||
}
|
||||
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) {
|
||||
verdict.hidden = false;
|
||||
verdict.textContent = ok
|
||||
? (quiz.dataset.quizRight || "Correct")
|
||||
: (quiz.dataset.quizWrong || "Not quite");
|
||||
verdict.classList.toggle("quiz-ok", ok);
|
||||
verdict.classList.toggle("quiz-bad", !ok);
|
||||
}
|
||||
|
||||
// a question-level explanation backs up a wrong answer as a whole
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = ok;
|
||||
|
||||
if (ok) right++;
|
||||
});
|
||||
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) {
|
||||
score.hidden = false;
|
||||
render(score, quiz.dataset.quizPoints || "{n}/{m}", scored, available);
|
||||
}
|
||||
}
|
||||
|
||||
function reset(quiz) {
|
||||
options(quiz).forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (box) box.checked = false;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-verdict").forEach(function (v) {
|
||||
v.hidden = true;
|
||||
v.textContent = "";
|
||||
v.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-q-score").forEach(function (b) {
|
||||
b.hidden = true;
|
||||
b.textContent = "";
|
||||
b.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-why-q").forEach(function (w) { w.hidden = true; });
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) { score.textContent = ""; score.hidden = false; }
|
||||
}
|
||||
|
||||
document.addEventListener("click", function (event) {
|
||||
var target = event.target;
|
||||
if (!target.closest) return;
|
||||
|
||||
var check = target.closest(".quiz .quiz-check");
|
||||
if (check) {
|
||||
judge(check.closest(".quiz"));
|
||||
return;
|
||||
}
|
||||
var again = target.closest(".quiz .quiz-reset");
|
||||
if (again) {
|
||||
reset(again.closest(".quiz"));
|
||||
}
|
||||
});
|
||||
|
||||
// Re-ticking a box after checking clears that row's verdict, so a stale
|
||||
// green or red never sits next to a box the reader has just changed — and
|
||||
// with it the question's badge and the headline, which would otherwise
|
||||
// still claim a score for an answer that has since moved.
|
||||
document.addEventListener("change", function (event) {
|
||||
var box = event.target;
|
||||
if (!box.closest || !box.classList || !box.classList.contains("quiz-box")) return;
|
||||
var opt = box.closest(".quiz-opt");
|
||||
if (!opt) return;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
|
||||
var q = opt.closest(".quiz-q");
|
||||
if (q) {
|
||||
var badge = q.querySelector(".quiz-q-score");
|
||||
if (badge) { badge.hidden = true; badge.textContent = ""; }
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) { verdict.hidden = true; verdict.textContent = ""; }
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = true;
|
||||
}
|
||||
var quiz = opt.closest(".quiz");
|
||||
if (quiz) {
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) score.textContent = "";
|
||||
}
|
||||
});
|
||||
})();
|
||||
+40
-16
@@ -36,7 +36,7 @@ ul.task-list li input[type="checkbox"] {
|
||||
<script src="site_libs/quarto-search/fuse.min.js"></script>
|
||||
<script src="site_libs/quarto-search/quarto-search.js"></script>
|
||||
<meta name="quarto:offset" content="./">
|
||||
<link href="./04-part-iv-rewind.html" rel="prev">
|
||||
<link href="./08-part-ix-mqtt.html" rel="prev">
|
||||
<script src="site_libs/quarto-html/quarto.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/tabsets/tabsets.js" type="module"></script>
|
||||
<script src="site_libs/quarto-html/popper.min.js"></script>
|
||||
@@ -51,19 +51,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -509,6 +509,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Part IV — Rewind</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Part V — Replay the dynamic idea across processes</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Part VI — Replay it over Syncthing, and name the messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Part VII — Now merge the two architectural ideas</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Part IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -1211,8 +1235,8 @@ Every entry here is defined in the chapter where the term first does some
|
||||
</script>
|
||||
<nav class="page-navigation">
|
||||
<div class="nav-page nav-page-previous">
|
||||
<a href="./04-part-iv-rewind.html" class="pagination-link" aria-label="[Part IV — Rewind]{.en}[Partie IV — Rembobinage]{.fr}[Teil IV — Zurückspulen]{.de}">
|
||||
<i class="bi bi-arrow-left-short"></i> <span class="nav-page-text"><span class="chapter-number">5</span> <span class="chapter-title">Part IV — Rewind</span></span>
|
||||
<a href="./08-part-ix-mqtt.html" class="pagination-link" aria-label="[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}">
|
||||
<i class="bi bi-arrow-left-short"></i> <span class="nav-page-text"><span class="chapter-number">9</span> <span class="chapter-title">Part IX — MQTT</span></span>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-page nav-page-next">
|
||||
|
||||
+39
-15
@@ -7,7 +7,7 @@
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
|
||||
|
||||
<meta name="author" content="Romain De Groote">
|
||||
<meta name="dcterms.date" content="2026-10-06">
|
||||
<meta name="dcterms.date" content="2026-10-16">
|
||||
|
||||
<title>Process Control</title>
|
||||
<style>
|
||||
@@ -53,19 +53,19 @@ ul.task-list li input[type="checkbox"] {
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme" id="quarto-bootstrap" data-mode="light">
|
||||
<link href="site_libs/bootstrap/bootstrap-dark-0fb591fb534e4de6e0a74f855bd29ac7.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme quarto-color-alternate" id="quarto-bootstrap" data-mode="dark">
|
||||
<link href="site_libs/bootstrap/bootstrap-e333b860288efea83b591af437d45305.min.css" rel="stylesheet" append-hash="true" class="quarto-color-scheme-extra" id="quarto-bootstrap" data-mode="light">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.0.0/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.0.0/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-1.0.0/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-1.0.0/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-1.0.0/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-1.0.0/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.0.0/glossary.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-exo-2.9.1/exo.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-exo-2.9.1/exo.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-quiz-2.9.1/quiz.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-further-2.9.1/further.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-latex-tables-2.9.1/latex-tables.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/theme.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/high-contrast.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/calc-notes.css" rel="stylesheet">
|
||||
<link href="site_libs/quarto-contrib/calc-notes-2.9.1/narrow.css" rel="stylesheet">
|
||||
<script src="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.js"></script>
|
||||
<link href="site_libs/quarto-contrib/calc-glossary-2.9.1/glossary.css" rel="stylesheet">
|
||||
<script id="quarto-search-options" type="application/json">{
|
||||
"location": "sidebar",
|
||||
"copy-button": false,
|
||||
@@ -511,6 +511,30 @@ ul.task-list li input[type="checkbox"] {
|
||||
<a href="./04-part-iv-rewind.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">5</span> <span class="chapter-title">Part IV — Rewind</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./05-part-v-subscriptions.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">6</span> <span class="chapter-title">Part V — Replay the dynamic idea across processes</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./06-part-vi-vocabulary.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">7</span> <span class="chapter-title">Part VI — Replay it over Syncthing, and name the messages</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./07-part-vii-mediation.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">8</span> <span class="chapter-title">Part VII — Now merge the two architectural ideas</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item">
|
||||
<div class="sidebar-item-container">
|
||||
<a href="./08-part-ix-mqtt.html" class="sidebar-item-text sidebar-link">
|
||||
<span class="menu-text"><span class="chapter-number">9</span> <span class="chapter-title">Part IX — MQTT</span></span></a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="sidebar-item sidebar-item-section">
|
||||
<div class="sidebar-item-container">
|
||||
@@ -569,7 +593,7 @@ ul.task-list li input[type="checkbox"] {
|
||||
<div>
|
||||
<div class="quarto-title-meta-heading">Published</div>
|
||||
<div class="quarto-title-meta-contents">
|
||||
<p class="date">6 October 2026</p>
|
||||
<p class="date">16 October 2026</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
+231
-1
@@ -324,11 +324,241 @@
|
||||
"href": "04-part-iv-rewind.html#sec-route-topic-intent",
|
||||
"title": "5 Part IV — Rewind",
|
||||
"section": "5.4 ROUTE and TOPIC are Intent",
|
||||
"text": "5.4 ROUTE and TOPIC are Intent\nApply two tests to TOPIC consoleIn.outbox. Does it describe something that happened? No. Something currently true? No. It says please begin listening here — desired behaviour, which is Intent. The mediator’s ROUTE is the same kind of message: please forward from here to there.\nOne trap worth naming, because it is tempting in a defence: publishing an Intent is of course something that happened. Classification follows what the message says, not the fact that it exists.\nAnd one condition, which returns later: the dynamic version is not automatically superior. It makes sense only if the consumer actually understands the producer’s message contract.\nSTATIC MEDIATED DYNAMIC DIRECT\nProducer → Mediator → Consumer Intent → (Producer ──► Consumer)",
|
||||
"text": "5.4 ROUTE and TOPIC are Intent\nApply two tests to TOPIC consoleIn.outbox. Does it describe something that happened? No. Something currently true? No. It says please begin listening here — desired behaviour, which is Intent. The mediator’s ROUTE is the same kind of message: please forward from here to there.\nOne trap worth naming, because it is tempting in a defence: publishing an Intent is naturally something that happened. Classification follows what the message says, not the fact that it exists.\nAnd one condition, which returns later: the dynamic version is not automatically superior. It makes sense only if the consumer actually understands the producer’s message contract.\nSTATIC MEDIATED DYNAMIC DIRECT\nProducer → Mediator → Consumer Intent → (Producer ──► Consumer)",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>5</span> <span class='chapter-title'>[Part IV — Rewind]{.en}[Partie IV — Rembobinage]{.fr}[Teil IV — Zurückspulen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html",
|
||||
"href": "05-part-v-subscriptions.html",
|
||||
"title": "6 Part V — Replay the dynamic idea across processes",
|
||||
"section": "",
|
||||
"text": "6.1 One blocking watch is not enough\nSteps 35 to 38 take the subscription idea out of the single JVM. The services become separate programs again, but instead of mediators copying files, each service watches the mailbox it was told to watch. One assumption of the first filesystem helper does not survive the move, and fixing it is what this part is really about.\nFileMessageBoard.watch(topic, receiver) registers one directory and blocks forever. That was enough while every process watched one fixed mailbox. A dynamically wired service needs more:\nThe old signature cannot express that, and the consequence was already visible earlier: the configurable mediator accepted exactly one ROUTE, because the moment it began watching its source it went deaf to its own control inbox. The limitation was never whose directory — it was one, fixed, forever.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-watch-limit",
|
||||
"href": "05-part-v-subscriptions.html#sec-watch-limit",
|
||||
"title": "6 Part V — Replay the dynamic idea across processes",
|
||||
"section": "",
|
||||
"text": "always watch its own control inbox\nAND\nadd a watched directory at runtime\nAND\npossibly remove it later",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-filesubscriptions",
|
||||
"href": "05-part-v-subscriptions.html#sec-filesubscriptions",
|
||||
"title": "6 Part V — Replay the dynamic idea across processes",
|
||||
"section": "6.2 The helper: FileSubscriptions",
|
||||
"text": "6.2 The helper: FileSubscriptions\nOne WatchService can serve many directories. register(...) returns a WatchKey identifying one of them, watcher.take() returns whichever key has events, and key.cancel() deregisters it. The helper keeps both directions, name → key and key → name, so an event can be traced back to the mailbox it came from.\nEvents do not reach a callback directly. They go onto a queue, read with take(), carrying\nrecord IncomingMessage(String mailbox, Message message) {}\nTwo reasons, and order of arrival is only the third. First, the observing thread must stay responsive for every subscribed directory: a callback that transformed, published or blocked would stall the observation of all the others. Second, the mailbox name travels with the message, so one loop in the service can decide what a message means — control inbox, so this is Intent to act on; subscribed source, so this is data to transform — and that same loop is free to add or remove subscriptions, because it is not sitting inside a callback.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "05-part-v-subscriptions.html#sec-two-publications",
|
||||
"href": "05-part-v-subscriptions.html#sec-two-publications",
|
||||
"title": "6 Part V — Replay the dynamic idea across processes",
|
||||
"section": "6.3 Two publications instead of four",
|
||||
"text": "6.3 Two publications instead of four\nRun SensorService, DynamicProcessorService and DynamicActuatorService — and no mediators — then let Configure.java publish the two TOPIC messages. A line typed afterwards leaves exactly two application publications in the board:\n\n\n\nmailbox\ncontent\nwhat it is\n\n\n\n\nconsoleIn/outbox\nTEXT hello\nthe input\n\n\nrot13/outbox\nTEXT uryyb\nthe result\n\n\nrot13/inbox\nTOPIC consoleIn/outbox\nIntent, published once\n\n\nconsoleOut/inbox\nTOPIC rot13/outbox\nIntent, published once\n\n\n\nconsoleOut/inbox holds no payload at all: ConsoleOut takes straight from rot13/outbox. Its inbox changed job, from carrying messages to carrying wiring.\nA line typed before Configure.java ran stays in consoleIn/outbox forever. A subscription that does not exist yet misses what came before it — exactly what the restarted mediator showed when it delivered nothing.\n\n\n\nversion\napplication publications\nprocesses in the data path\n\n\n\n\nmediated (step 18)\n4\n5\n\n\nconfigurable mediator (step 27)\n4\n5\n\n\ndynamic (step 38)\n2\n3",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>6</span> <span class='chapter-title'>[Part V — Replay the dynamic idea across processes]{.en}[Partie V — Rejouer l'idée dynamique entre processus]{.fr}[Teil V — Die dynamische Idee über Prozesse hinweg wiederholen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html",
|
||||
"href": "06-part-vi-vocabulary.html",
|
||||
"title": "7 Part VI — Replay it over Syncthing, and name the messages",
|
||||
"section": "",
|
||||
"text": "7.1 The distributed dynamic run\nSteps 39 to 47 distribute the dynamic version across two machines, say precisely what “direct” means, and then — only now, after the ideas have been used — give the three kinds of message their names: Intent, Status, Event.\nSensor on one machine, ROT13 and the actuator on the other, no mediator anywhere. After the two TOPIC Intents had replicated, a typed line produced the result on the other machine — and the board shows what that cost:\nThe timing was the interesting part. The input was published at 02:35:12 and the results appeared on the first machine at 04:11:28.797 and .893 — 96 ms apart, long after the input. Syncthing had been saturated overnight, so the batch arrived when the queue drained. The chain was correct throughout; the transport’s latency is simply not something the architecture controls. Compare 24 ms for the same chain on one machine.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-distributed-dynamic",
|
||||
"href": "06-part-vi-vocabulary.html#sec-distributed-dynamic",
|
||||
"title": "7 Part VI — Replay it over Syncthing, and name the messages",
|
||||
"section": "",
|
||||
"text": "consoleIn/outbox: the input;\nrot13/outbox: the result, written by the service that produced it;\nconsoleOut/inbox: Intent only, where the mediated version held a full copy of every message.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-direct-precisely",
|
||||
"href": "06-part-vi-vocabulary.html#sec-direct-precisely",
|
||||
"title": "7 Part VI — Replay it over Syncthing, and name the messages",
|
||||
"section": "7.2 What “direct” means, exactly",
|
||||
"text": "7.2 What “direct” means, exactly\nTwo hops that look alike are architecturally opposite:\n\na transport hop — Syncthing on each side, possibly a relay in between — adds no participant that knows the topology and nothing reacts to it. If the packets detoured through another continent, no claim here would be contradicted.\nan architectural hop — a mediator copying consoleIn/outbox → rot13/inbox — adds a component that must know both names, sits in the availability chain, and republishes the message.\n\nSo the defensible claim is: ROT13 reacts to ConsoleIn’s publication with no component of ours in between, and without containing ConsoleIn’s identity. Not: the data goes straight from A to B. The architecture controls which messages a service reacts to, not the transport’s routing.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-ise",
|
||||
"href": "06-part-vi-vocabulary.html#sec-ise",
|
||||
"title": "7 Part VI — Replay it over Syncthing, and name the messages",
|
||||
"section": "7.3 Intent, Status, Event",
|
||||
"text": "7.3 Intent, Status, Event\nThree kinds of message, named only after being used:\n\n\n\n\n\n\n\n\n\nsays\nour examples\n\n\n\n\nE — Event\nsomething happened\nTEXT hello as ConsoleIn/E/text; TEXT uryyb as ROT13/E/crypted\n\n\nS — Status/State\nsomething is currently true\nROT13/S/subscriptions — not published by our system yet\n\n\nI — Intent\nwhat should happen\nTOPIC consoleIn/outbox, ROUTE … …\n\n\n\nPast tense is a useful hint for Events. For Intent the test is two questions: does the message report something that happened? No. Something currently true? No. Then it requests behaviour.\nOne trap: publishing an Intent is naturally something that happened. Classify by what the message says, not by the fact that it exists — otherwise every message becomes an Event and the vocabulary stops being useful.\nStatus deserves its own note, because the instinct is to ask for it: “what are your subscriptions?” But asking is a call, and a call needs the asker to know the component, to know it is up, and to wait. Status is published: ROT13 publishes ROT13/S/subscriptions whenever its wiring changes, and anyone interested reads it. The reader then needs a topic, not a component, and ROT13 never learns who audits it. Each kind answers a different question:\n\nan Event is only useful if you were listening — our stranded messages, three times over;\na Status is what a newcomer needs: the current value, without replaying history;\nan Intent asks for a change.\n\nAnd commands are not forbidden. Sending ROT13/I with ACTION Hello is command-like, and the material’s verdict is “Fine.” The component performs its capability and publishes its Events and its Status. The flow it endorses is Intent → component → State + Events.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "06-part-vi-vocabulary.html#sec-one-writer",
|
||||
"href": "06-part-vi-vocabulary.html#sec-one-writer",
|
||||
"title": "7 Part VI — Replay it over Syncthing, and name the messages",
|
||||
"section": "7.4 The one-writer rule",
|
||||
"text": "7.4 The one-writer rule\n\nEvery writable resource has exactly one writer authority.\n\nDo not confuse that with the UUID in a message filename. The UUID prevents two publications from choosing the same physical name; writer authority says which component owns a logical Event or Status resource. Two writers never collide on a filename, and that is exactly why the problem is easy to miss.\nWhat a second writer costs: the mailbox name was the only provenance marker, so rot13/outbox stops meaning “ROT13 transformed this” and a subscriber can no longer trust the contract it built on. For Status it is worse — two components each claiming to publish the current value of one fact simply contradict each other, with no ordering guarantee across machines to break the tie. For append-only Events many publications coexist by design; the question is semantic ownership, not collision. When two authorities appear, ask why there are two rather than reaching for a lock.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>7</span> <span class='chapter-title'>[Part VI — Replay it over Syncthing, and name the messages]{.en}[Partie VI — Rejouer sur Syncthing, et nommer les messages]{.fr}[Teil VI — Über Syncthing wiederholen und die Nachrichten benennen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html",
|
||||
"href": "07-part-vii-mediation.html",
|
||||
"title": "8 Part VII — Now merge the two architectural ideas",
|
||||
"section": "",
|
||||
"text": "8.1 A transformer earns its existence\nTwo mediators were removed and the gain was measured. Steps 48 to 52 answer the obvious next question: does that make mediation wrong? No — and the distinction that decides it is sharp enough to apply to a design you have never seen.\nWhat was removed was a mediator computing A → A: an expensive identity function, in the availability chain, copying every message without adding meaning.\nNow take a producer publishing {\"value\":\"Hello\"} and a consumer expecting a display structure. A TextToDisplayTransformer between them contributes schema transformation, semantic adaptation, possibly unit conversion, possibly aggregation. That is work neither side should own: ROT13 is not meant to decide terminal colours, and the console is not meant to understand ROT13’s payload shape.\nThe line is drawn by contract compatibility, not by whether something is added. A mediator converting Celsius to Fahrenheit changes rather than adds and has earned its place; one appending a timestamp to a message the consumer already understands has added something and is still suspicious. The question is always: could the consumer read the producer’s message as it stands?",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-transformer",
|
||||
"href": "07-part-vii-mediation.html#sec-transformer",
|
||||
"title": "8 Part VII — Now merge the two architectural ideas",
|
||||
"section": "",
|
||||
"text": "If a consumer semantically understands a producer’s publication, direct subscription is often sufficient. If the contracts are incompatible, introduce a transformer that performs an actual adaptation.\nA mediator that merely forwards compatible data is suspicious. A mediator that adds necessary semantics has earned its existence.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-egoistic-transformer",
|
||||
"href": "07-part-vii-mediation.html#sec-egoistic-transformer",
|
||||
"title": "8 Part VII — Now merge the two architectural ideas",
|
||||
"section": "8.2 The transformer is egoistic too",
|
||||
"text": "8.2 The transformer is egoistic too\nInserted into the chain, the transformer subscribes to rot13/outbox and publishes to its own outbox; ConsoleOut then subscribes to the transformer’s outbox instead of ROT13’s. Note what that costs in code: nothing. ConsoleOut receives a different Intent — TOPIC display/outbox rather than TOPIC rot13/outbox — and the chain is rewired. ROT13 never learns the transformer exists; the transformer never learns ConsoleOut exists.\nWhy not let it publish straight into consoleOut/inbox, saving a mailbox? Four reasons:\n\nknowledge — it would contain ConsoleOut’s name, which is topology inside a service, the relapse of step 28;\nownership — that inbox is ConsoleOut’s control channel, written by the configurator; payload from the transformer would give it two authorities;\nreach — its own outbox can be read by a logger, a web view or a second display at no cost, while one inbox serves exactly one consumer;\nmutability — an aggregator can later be inserted after it by sending one different Intent, with no component edited.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "07-part-vii-mediation.html#sec-complete-filesystem",
|
||||
"href": "07-part-vii-mediation.html#sec-complete-filesystem",
|
||||
"title": "8 Part VII — Now merge the two architectural ideas",
|
||||
"section": "8.3 The complete filesystem architecture",
|
||||
"text": "8.3 The complete filesystem architecture\nEvery mailbox with exactly one writer:\n\n\n\n\n\n\n\nmailbox\nsingle writer\n\n\n\n\nconsoleIn/outbox\nSensorService\n\n\nrot13/outbox\nProcessorService\n\n\ndisplay/outbox\nthe transformer\n\n\nevery control inbox\nthe configurator — the one designated Intent authority\n\n\nthe terminal\nActuatorService, which writes no mailbox at all\n\n\n\nEgoistic capabilities, Intent from one authority, a transformer only where contracts differ, one writer per resource, and the topology nowhere in the capabilities. That is the design the filesystem was good enough to teach — and the next part asks what the filesystem itself is no longer good enough for.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>8</span> <span class='chapter-title'>[Part VII — Now merge the two architectural ideas]{.en}[Partie VII — Fusionner les deux idées architecturales]{.fr}[Teil VII — Die zwei architektonischen Ideen zusammenführen]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html",
|
||||
"href": "08-part-ix-mqtt.html",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "",
|
||||
"text": "9.1 What the filesystem taught, and what it is not for\nThe filesystem taught publication boundaries, directories as addresses, observation, independent processes, independent languages, synchronisation latency, runtime wiring, State, Intent, Events, mediator costs, service ownership and transformer services. It was a good teacher and it is not an elegant message broker: by the end the architecture was clean and the transport was a pile of .tmp files, atomic moves, rescanning, shared paths and replication delay.\nThe conclusion is not “files bad, MQTT good”. The filesystem has an advantage MQTT cannot match — it routinely stores gigabytes or terabytes, while brokers and clients are built for small messages, and chunking a huge payload over MQTT means inventing a file-transfer protocol inside a message protocol. So:\nA replicated filesystem also gives every machine a local copy, which is a genuine strength — though replication is not a backup: deletion and corruption replicate too, unless versioning preserves older copies.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-filesystem-verdict",
|
||||
"href": "08-part-ix-mqtt.html#sec-filesystem-verdict",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "",
|
||||
"text": "Use messages for coordination and events. Use an appropriate file or object store for large data. A message can carry the location, identity and metadata of that data instead of the terabytes themselves.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-mqtt-mapping",
|
||||
"href": "08-part-ix-mqtt.html#sec-mqtt-mapping",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "9.2 MQTT should look familiar",
|
||||
"text": "9.2 MQTT should look familiar\n\n\n\nfilesystem / Syncthing\nMQTT\n\n\n\n\nsynchronised message-board root\nbroker / namespace\n\n\ndirectory path\ntopic\n\n\n.msg file\npublication\n\n\nfile contents\npayload\n\n\nWatchService\nsubscription\n\n\ndynamic directory\ntopic / filter\n\n\ncontrol directory\nI\n\n\nstate directory\nS/…\n\n\nevent directory\nE/…\n\n\n\nThe reaction the material is after: “Oh. We already know this architecture.” MQTT is a transport change, not an architectural claim.\nTwo things a directory could not do, both visible in a minute at the command line. A publication made before a subscriber exists never reaches it — the stranded-message problem for the third time, now with an answer the filesystem never had. And a filter like test/# matches test/a and test/a/b/c but not testing/x, because # works on levels, not string prefixes; test/+ would match only one level down.\nThe deeper correction: a topic is not a container. There is no object called test/a on the broker. A topic is a routing key carried by each publication and matched against the filters of whoever is subscribed at that instant. Directories hold messages; topics match them. One subscription therefore covers topics that do not exist yet — where a message board needed a new directory and a new registration.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-paho",
|
||||
"href": "08-part-ix-mqtt.html#sec-paho",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "9.3 The library, the client id and the broker address",
|
||||
"text": "9.3 The library, the client id and the broker address\nJava has no MQTT client in its standard library, so Paho arrives now — after the need, like the mediator in step 7 and Jackson in step 64. Four things are needed from it: connect, publish, subscribe, callback. Connecting is deliberately anticlimactic: “Nothing architectural happened here. We merely attached our process to the transport.”\nTwo details of connecting carry weight:\n\nthe client id is not merely a uniqueness token. The broker recognises a returning client by it and keeps session state for it: subscriptions, messages queued at QoS > 0, and the association with its Last Will. A directory never knew who was watching, which is exactly why a restarted watcher’s backlog was never replayed.\nthe broker address is deployment configuration: every runnable reads System.getProperty(\"mqtt.broker\", \"tcp://localhost:1883\"). It is also the one piece of configuration that cannot arrive as Intent, because Intent travels through the broker. Topology can be published; the address of the thing that publishes it cannot.\n\nSubscribing costs one packet, and the broker keeps the subscription list. There is no standard way to ask it what another client subscribed to — which is why S/subscriptions exists: a component’s own declaration of its wiring, published so the architecture can know what the transport keeps private. Only its owner may publish it, by the one-writer rule, because only its owner knows what it accepted.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-structured-intent",
|
||||
"href": "08-part-ix-mqtt.html#sec-structured-intent",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "9.4 Structured Intent, and two object mappers",
|
||||
"text": "9.4 Structured Intent, and two object mappers\nTOPIC some/path has one field and one meaning. It cannot say which kind of Intent this is, carry a second parameter, nest, or be extended; and there is nothing for a receiver to validate against. Richer Intent wants structure:\nsubscribe:\n topic: Demo/ConsoleIn/U/alice/E/text\nOnly then does a serialisation library have a clear job. JsonTools keeps two mappers, and the asymmetry is deliberate:\n\nreading uses a YAML factory with FAIL_ON_UNKNOWN_PROPERTIES off — JSON is a subset of YAML, so hand-typed Intent is accepted, and a newer configurator can send fields an older service ignores;\nwriting uses plain JSON with INDENT_OUTPUT on, so published payloads are strict and readable.\n\nTolerant in, strict out. A single shared mapper would have to give up one of those.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-duise",
|
||||
"href": "08-part-ix-mqtt.html#sec-duise",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "9.5 DUISE, and rewiring a running system",
|
||||
"text": "9.5 DUISE, and rewiring a running system\nThe naming scheme finally gets its name: Description (what contracts this service understands and publishes), Unit (which instance), Intent (requested behaviour), Status (what is true now), Event (what happened).\nDemo/ROT13/U/alice/{I, S/online, S/subscriptions/text, E/crypted}\nU/<unit> is what the filesystem never needed: each machine had its own replica of the same relative path, so instance identity was implicit. MQTT has one shared namespace, so a topic must say which copy. Hard-coding U/alice in a capability is therefore worse than hard-coding consoleIn.outbox ever was: it binds the build to one deployment. Configured by Intent, one build serves everyone — which is why MqttConfigure takes three unit names as arguments. The unit names are the topology.\nRewiring, observed on a running system: publish a new Intent naming a different source topic, and the service unsubscribes from the old one, subscribes to the new one, and republishes S/subscriptions to match. No restart, no edit. Send an invalid filter instead — Demo/#/E/text, where # is not the last level — and MqttTools.isValidFilter rejects it; the old subscription stands and the Status still tells the truth.\nThat rejection exposes a real gap, worth naming rather than hiding: it is logged locally only. The configurator cannot tell whether its Intent was applied or refused, and a monitor cannot distinguish “refused” from “not yet processed”. In this design a sender learns the outcome by reading Status and comparing it with what it asked for. Publishing refusals as an Event, or a last-error Status, would close that gap; neither is in the material, so it is a design decision to justify.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-retained-and-will",
|
||||
"href": "08-part-ix-mqtt.html#sec-retained-and-will",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "9.6 What a new subscriber learns, and what a dead one admits",
|
||||
"text": "9.6 What a new subscriber learns, and what a dead one admits\nSubscribing to Demo/# for three seconds, with nothing being published, returns this:\nDemo/ROT13/U/nitro5/S/online {\"value\":true}\nDemo/ROT13/U/nitro5/S/subscriptions/text \"Demo/ConsoleIn/U/nitro5/E/text\"\nDemo/ConsoleOut/U/nitro5/S/online {\"value\":true}\nDemo/ConsoleOut/U/nitro5/S/subscriptions/text \"Demo/ROT13/U/nitro5/E/crypted\"\nA late arrival learns the entire current wiring of the system, instantly, without asking anyone and without any component knowing a monitor exists. That is retained Status. No Events arrive, because Events are published non-retained — “retained State, non-retained Events”. It is also the proper answer to the instinct of asking a service what it is doing: nobody asks; the service states it, once, and the broker keeps it for whoever turns up.\nRetained Status alone would lie, though. Kill a service with Ctrl+C and its S/online = true stays on the broker forever. Hence the Last Will, registered at connect time:\nvar will = new MqttMessage(\"{\\\"value\\\":false}\".getBytes(UTF_8), 1, true, new MqttProperties());\noptions.setWill(lastWillTopic, will);\nThe will is retained, so when the broker publishes it on the client’s behalf it replaces the stale true. The component that fails is not the component that reports the failure — which is the only arrangement that can work. One caveat: a clean DISCONNECT does not trigger a will, so a well-behaved service publishes online=false itself on the way out, and the will covers the ugly deaths.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-coupling-remains",
|
||||
"href": "08-part-ix-mqtt.html#sec-coupling-remains",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "9.7 What survived the transport, and what coupling remains",
|
||||
"text": "9.7 What survived the transport, and what coupling remains\nThe lower half of the filesystem→MQTT table is the point: I, S, E, egoistic services, runtime topology and “transformer if needed” are unchanged. The architecture survived the transport replacement, and that is the strongest available evidence that the architecture was never about the transport.\nLoose coupling does not mean nothing knows anything. What remains, necessarily, is agreement on: message syntax, message semantics, topic contracts, Intent, ownership, the meaning of State and the meaning of Events. The goal is not to eliminate coupling but to eliminate unnecessary knowledge. Concretely, in this system each service must understand exactly one foreign Event contract — ROT13 understands ConsoleIn’s E/text, ConsoleOut understands ROT13’s E/crypted — plus the Intent schema it accepts on its own I. That list is the irreducible minimum.\nSeparately, the broker is a shared infrastructure dependency: everyone needs its address and nothing works without it. Real, but a different kind of thing from one component knowing another.\nThe step-78 checklist is the tool to keep. Twelve questions, of which these six carry the argument for this system:\n\n\n\n\n\n\n\nquestion\nanswer here\n\n\n\n\ndoes a capability contain a hard-coded producer identity?\nno — it arrives as Intent\n\n\nwhich foreign contracts must it understand?\none Event contract each, plus its own Intent schema\n\n\nwhere is topology defined?\nin the configurator, outside the data path\n\n\ncan topology change without recompiling?\nyes — demonstrated on a running system\n\n\ncould the transport be replaced?\nyes — demonstrated, filesystem then MQTT\n\n\ndoes every mediator do something that needs mediation?\nyes, vacuously: TEXT → TEXT needs none, and none exists\n\n\n\nThe material’s own caution applies: the answers need not all be “no”. They need to be intentional.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-whole-journey",
|
||||
"href": "08-part-ix-mqtt.html#sec-whole-journey",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "9.8 The whole journey",
|
||||
"text": "9.8 The whole journey\nThe program never changed: a line goes in, the same line comes out rotated by 13 letters. What changed, eleven times, is how the parts are joined and who holds the knowledge of how they are joined.\n\n\n\n\n\n\n\n\n\nstage\nhow the parts are joined\nwhere the topology lives\nin the data path besides the capabilities\n\n\n\n\n1 procedural\ndirect calls\ninside the capability code\n—\n\n\n2 egoistic services\nnot joined at all\nnowhere — that is the problem\n—\n\n\n3 static mediation, one JVM\nmailboxes, copied by mediators\nthe mediators, started in main()\ntwo mediators\n\n\n4 static mediation, filesystem\ndirectories, copied by mediator processes\nthe operator’s command lines\ntwo mediator processes\n\n\n5 static mediation, Syncthing\nreplicated directories\nthe operator’s command lines\ntwo mediator processes, plus replication delay\n\n\n6 named, configurable mediators\nROUTE Intent from an orchestrator\nthe orchestrator, outside the path\nthe mediators, still\n\n\n7 dynamic, one JVM\nservices listen, told by TOPIC Intent\nthe configurator\nnothing\n\n\n8 dynamic, filesystem\nthe same, over directories\nthe configurator\nnothing\n\n\n9 dynamic, Syncthing\nthe same, over replicated directories\nthe configurator\nnothing — transport hops only\n\n\n10 contracts\ncompatible: direct; incompatible: a transformer\nthe configurator\na transformer, only where contracts differ\n\n\n11 MQTT\ntopics on a broker\nthe configurator\nnothing — the broker is transport\n\n\n\nRead the third column from top to bottom: the topology moves outward, one stage at a time, until no capability holds any of it. Read the last one: the price of that move falls to zero at stage 7 and stays there while the transport changes underneath three times. Same architecture, better transport.",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "08-part-ix-mqtt.html#sec-sentences",
|
||||
"href": "08-part-ix-mqtt.html#sec-sentences",
|
||||
"title": "9 Part IX — MQTT",
|
||||
"section": "9.9 The sentences to remember",
|
||||
"text": "9.9 The sentences to remember\n\nEvent-driven describes how information and control flow.\nLoose coupling describes how much participants need to know about one another.\nPublish what happened.\nDeclare what you want.\nPublish your own State.\nKeep capabilities egoistic.\nKeep topology out of capabilities.\nDo not pay for a mediator unless it actually mediates something.\n\nAnd whenever an architecture becomes confusing, go back to the first question of this book: who knows whom?",
|
||||
"crumbs": [
|
||||
"<span class='chapter-number'>9</span> <span class='chapter-title'>[Part IX — MQTT]{.en}[Partie IX — MQTT]{.fr}[Teil IX — MQTT]{.de}</span>"
|
||||
]
|
||||
},
|
||||
{
|
||||
"objectID": "glossary.html",
|
||||
"href": "glossary.html",
|
||||
|
||||
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
@@ -1,126 +0,0 @@
|
||||
// quiz — judge the tick boxes of one quiz, explain what went wrong
|
||||
//
|
||||
// Every label the reader sees is written into the markup by quiz.lua, so the
|
||||
// wording follows the book's language and nothing is translated twice. A
|
||||
// quiz carries:
|
||||
// data-quiz-score "{n} of {m} questions correct" ({n}/{m} substituted)
|
||||
// data-quiz-right verdict of a question answered correctly
|
||||
// data-quiz-wrong verdict of a question answered wrongly
|
||||
//
|
||||
// A question is right only when every one of its options is in the right
|
||||
// state: ticked when true, left empty when false. That is the "multiple
|
||||
// true/false" rule of the exam, and it is why a half-ticked question counts
|
||||
// as wrong.
|
||||
(function () {
|
||||
"use strict";
|
||||
|
||||
function options(quiz) {
|
||||
return quiz.querySelectorAll(".quiz-opt");
|
||||
}
|
||||
|
||||
function judge(quiz) {
|
||||
var questions = quiz.querySelectorAll(".quiz-q");
|
||||
var right = 0;
|
||||
|
||||
questions.forEach(function (q) {
|
||||
var ok = true;
|
||||
|
||||
q.querySelectorAll(".quiz-opt").forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (!box) return;
|
||||
var want = opt.dataset.correct === "1";
|
||||
var hit = box.checked === want;
|
||||
|
||||
opt.classList.toggle("quiz-ok", hit);
|
||||
opt.classList.toggle("quiz-bad", !hit);
|
||||
|
||||
// the explanation of an option is for the reader who got it wrong
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = hit;
|
||||
|
||||
if (!hit) ok = false;
|
||||
});
|
||||
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) {
|
||||
verdict.hidden = false;
|
||||
verdict.textContent = ok
|
||||
? (quiz.dataset.quizRight || "Correct")
|
||||
: (quiz.dataset.quizWrong || "Not quite");
|
||||
verdict.classList.toggle("quiz-ok", ok);
|
||||
verdict.classList.toggle("quiz-bad", !ok);
|
||||
}
|
||||
|
||||
// a question-level explanation backs up a wrong answer as a whole
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = ok;
|
||||
|
||||
if (ok) right++;
|
||||
});
|
||||
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) {
|
||||
var template = quiz.dataset.quizScore || "{n}/{m}";
|
||||
score.innerHTML = "";
|
||||
// built as nodes, not markup: the template comes from metadata
|
||||
var parts = template.split(/\{n\}|\{m\}/);
|
||||
var values = [];
|
||||
(template.match(/\{n\}|\{m\}/g) || []).forEach(function (token) {
|
||||
values.push(token === "{n}" ? right : questions.length);
|
||||
});
|
||||
parts.forEach(function (text, i) {
|
||||
score.appendChild(document.createTextNode(text));
|
||||
if (i < values.length) {
|
||||
var b = document.createElement("b");
|
||||
b.textContent = String(values[i]);
|
||||
score.appendChild(b);
|
||||
}
|
||||
});
|
||||
}
|
||||
}
|
||||
|
||||
function reset(quiz) {
|
||||
options(quiz).forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (box) box.checked = false;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-verdict").forEach(function (v) {
|
||||
v.hidden = true;
|
||||
v.textContent = "";
|
||||
v.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-why-q").forEach(function (w) { w.hidden = true; });
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) score.textContent = "";
|
||||
}
|
||||
|
||||
document.addEventListener("click", function (event) {
|
||||
var target = event.target;
|
||||
if (!target.closest) return;
|
||||
|
||||
var check = target.closest(".quiz .quiz-check");
|
||||
if (check) {
|
||||
judge(check.closest(".quiz"));
|
||||
return;
|
||||
}
|
||||
var again = target.closest(".quiz .quiz-reset");
|
||||
if (again) {
|
||||
reset(again.closest(".quiz"));
|
||||
}
|
||||
});
|
||||
|
||||
// re-ticking a box after checking clears that row's verdict, so a stale
|
||||
// green or red never sits next to a box the reader has just changed
|
||||
document.addEventListener("change", function (event) {
|
||||
var box = event.target;
|
||||
if (!box.closest || !box.classList || !box.classList.contains("quiz-box")) return;
|
||||
var opt = box.closest(".quiz-opt");
|
||||
if (!opt) return;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(".quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
})();
|
||||
+40
@@ -113,6 +113,31 @@
|
||||
margin-top: 0.5rem;
|
||||
}
|
||||
|
||||
/* ---- the per-question points badge ---------------------------------- */
|
||||
|
||||
/* The head now always exists (it is where the badge lands), so an empty one
|
||||
on a single-question quiz must not leave a gap. */
|
||||
.quiz-q-head:empty { display: none; }
|
||||
|
||||
.quiz-q-head {
|
||||
display: flex;
|
||||
align-items: baseline;
|
||||
justify-content: space-between;
|
||||
gap: 0.6rem;
|
||||
}
|
||||
|
||||
.quiz-q-score {
|
||||
font-size: 0.82rem;
|
||||
font-weight: 400;
|
||||
color: var(--quiz-ink);
|
||||
white-space: nowrap;
|
||||
}
|
||||
.quiz-q-score b { color: var(--calc-notecolor, #B45309); font-weight: 600; }
|
||||
/* green and red stay reserved for a judged answer; the badge follows the
|
||||
verdict right below it so the two never disagree */
|
||||
.quiz-q-score.quiz-ok b { color: var(--quiz-ok); }
|
||||
.quiz-q-score.quiz-bad b { color: var(--quiz-bad); }
|
||||
|
||||
/* ---- verdict and bar ------------------------------------------------ */
|
||||
|
||||
.quiz-verdict {
|
||||
@@ -160,6 +185,18 @@
|
||||
|
||||
/* ---- dark theme ----------------------------------------------------- */
|
||||
|
||||
/* High contrast remaps the whole palette, and --quiz-ok / --quiz-bad are local
|
||||
to this file, so they have to be pointed at the HC pair by hand: without
|
||||
this the verdict and the points badge keep their ordinary-mode green and
|
||||
red, which is exactly what a reader turns HC on to avoid. `body` makes it
|
||||
outweigh body.quarto-dark .quiz below, or dark + HC would keep the plain
|
||||
dark pair. */
|
||||
html.hc body .quiz {
|
||||
--quiz-ok: var(--hc-success);
|
||||
--quiz-bad: var(--hc-danger);
|
||||
--quiz-ink: var(--hc-fg);
|
||||
}
|
||||
|
||||
body.quarto-dark .quiz {
|
||||
--quiz-ok: #4cb08a;
|
||||
--quiz-bad: #e2798f;
|
||||
@@ -174,5 +211,8 @@ body.quarto-dark .quiz {
|
||||
*/
|
||||
@media print {
|
||||
.quiz-bar { display: none; }
|
||||
/* on paper the points are printed in the statement by quiz.lua, so the
|
||||
screen badge would say the same thing twice */
|
||||
.quiz-q-score { display: none; }
|
||||
.quiz-opt.quiz-ok, .quiz-opt.quiz-bad { background: none; }
|
||||
}
|
||||
@@ -0,0 +1,183 @@
|
||||
// quiz — judge the tick boxes of one quiz, score it in points, explain mistakes
|
||||
//
|
||||
// Every label the reader sees is written into the markup by quiz.lua, so the
|
||||
// wording follows the book's language and nothing is translated twice. A
|
||||
// quiz carries:
|
||||
// data-quiz-score "{n} of {m} questions correct"
|
||||
// data-quiz-points "{n} of {m} points" (the headline)
|
||||
// data-quiz-qpoints "{n}/{m} points" (one question's badge)
|
||||
// data-quiz-right verdict of a question answered correctly
|
||||
// data-quiz-wrong verdict of a question answered wrongly
|
||||
// and each question carries data-points / data-penalty.
|
||||
//
|
||||
// SCORING. A question is worth data-points (default 3). Every statement whose
|
||||
// box disagrees with its truth value — an unticked true one, or a ticked false
|
||||
// one — costs data-penalty (default 1). The result floors at zero, so a
|
||||
// question can never drag the total down. The quiz total is the sum over its
|
||||
// questions. A question still counts as "correct" for the verdict line only
|
||||
// when every one of its statements is right, which is the exam's
|
||||
// multiple-true-false rule.
|
||||
(function () {
|
||||
"use strict";
|
||||
|
||||
function options(quiz) {
|
||||
return quiz.querySelectorAll(".quiz-opt");
|
||||
}
|
||||
|
||||
// Number(undefined) || 3 would also swallow a deliberate 0, so test first.
|
||||
function num(el, name, dflt) {
|
||||
var raw = el.dataset ? el.dataset[name] : null;
|
||||
if (raw === undefined || raw === null || raw === "") return dflt;
|
||||
var n = Number(raw);
|
||||
return isFinite(n) ? n : dflt;
|
||||
}
|
||||
|
||||
// Substitute {n} and {m} into a template from metadata, building text nodes
|
||||
// rather than markup: the template is author text, never trusted as HTML.
|
||||
function render(el, template, n, m) {
|
||||
el.innerHTML = "";
|
||||
var parts = template.split(/\{n\}|\{m\}/);
|
||||
var values = (template.match(/\{n\}|\{m\}/g) || []).map(function (token) {
|
||||
return token === "{n}" ? n : m;
|
||||
});
|
||||
parts.forEach(function (text, i) {
|
||||
el.appendChild(document.createTextNode(text));
|
||||
if (i < values.length) {
|
||||
var b = document.createElement("b");
|
||||
b.textContent = String(values[i]);
|
||||
el.appendChild(b);
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
function judge(quiz) {
|
||||
var questions = quiz.querySelectorAll(".quiz-q");
|
||||
var right = 0, scored = 0, available = 0;
|
||||
|
||||
questions.forEach(function (q) {
|
||||
var ok = true;
|
||||
var misses = 0;
|
||||
var pts = num(q, "points", 3);
|
||||
var pen = num(q, "penalty", 1);
|
||||
|
||||
q.querySelectorAll(".quiz-opt").forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (!box) return;
|
||||
var want = opt.dataset.correct === "1";
|
||||
var hit = box.checked === want;
|
||||
|
||||
opt.classList.toggle("quiz-ok", hit);
|
||||
opt.classList.toggle("quiz-bad", !hit);
|
||||
|
||||
// the explanation of an option is for the reader who got it wrong.
|
||||
// :scope > keeps this to the option's own .why — a question-level
|
||||
// .quiz-why-q also carries the class quiz-why.
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = hit;
|
||||
|
||||
if (!hit) { ok = false; misses++; }
|
||||
});
|
||||
|
||||
var got = Math.max(0, pts - misses * pen);
|
||||
scored += got;
|
||||
available += pts;
|
||||
|
||||
var badge = q.querySelector(".quiz-q-score");
|
||||
if (badge) {
|
||||
badge.hidden = false;
|
||||
render(badge, quiz.dataset.quizQpoints || "{n}/{m}", got, pts);
|
||||
badge.classList.toggle("quiz-ok", misses === 0);
|
||||
badge.classList.toggle("quiz-bad", got === 0 && pts > 0);
|
||||
}
|
||||
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) {
|
||||
verdict.hidden = false;
|
||||
verdict.textContent = ok
|
||||
? (quiz.dataset.quizRight || "Correct")
|
||||
: (quiz.dataset.quizWrong || "Not quite");
|
||||
verdict.classList.toggle("quiz-ok", ok);
|
||||
verdict.classList.toggle("quiz-bad", !ok);
|
||||
}
|
||||
|
||||
// a question-level explanation backs up a wrong answer as a whole
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = ok;
|
||||
|
||||
if (ok) right++;
|
||||
});
|
||||
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) {
|
||||
score.hidden = false;
|
||||
render(score, quiz.dataset.quizPoints || "{n}/{m}", scored, available);
|
||||
}
|
||||
}
|
||||
|
||||
function reset(quiz) {
|
||||
options(quiz).forEach(function (opt) {
|
||||
var box = opt.querySelector(".quiz-box");
|
||||
if (box) box.checked = false;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-verdict").forEach(function (v) {
|
||||
v.hidden = true;
|
||||
v.textContent = "";
|
||||
v.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-q-score").forEach(function (b) {
|
||||
b.hidden = true;
|
||||
b.textContent = "";
|
||||
b.classList.remove("quiz-ok", "quiz-bad");
|
||||
});
|
||||
quiz.querySelectorAll(".quiz-why-q").forEach(function (w) { w.hidden = true; });
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) { score.textContent = ""; score.hidden = false; }
|
||||
}
|
||||
|
||||
document.addEventListener("click", function (event) {
|
||||
var target = event.target;
|
||||
if (!target.closest) return;
|
||||
|
||||
var check = target.closest(".quiz .quiz-check");
|
||||
if (check) {
|
||||
judge(check.closest(".quiz"));
|
||||
return;
|
||||
}
|
||||
var again = target.closest(".quiz .quiz-reset");
|
||||
if (again) {
|
||||
reset(again.closest(".quiz"));
|
||||
}
|
||||
});
|
||||
|
||||
// Re-ticking a box after checking clears that row's verdict, so a stale
|
||||
// green or red never sits next to a box the reader has just changed — and
|
||||
// with it the question's badge and the headline, which would otherwise
|
||||
// still claim a score for an answer that has since moved.
|
||||
document.addEventListener("change", function (event) {
|
||||
var box = event.target;
|
||||
if (!box.closest || !box.classList || !box.classList.contains("quiz-box")) return;
|
||||
var opt = box.closest(".quiz-opt");
|
||||
if (!opt) return;
|
||||
opt.classList.remove("quiz-ok", "quiz-bad");
|
||||
var why = opt.querySelector(":scope > .quiz-why");
|
||||
if (why) why.hidden = true;
|
||||
|
||||
var q = opt.closest(".quiz-q");
|
||||
if (q) {
|
||||
var badge = q.querySelector(".quiz-q-score");
|
||||
if (badge) { badge.hidden = true; badge.textContent = ""; }
|
||||
var verdict = q.querySelector(".quiz-verdict");
|
||||
if (verdict) { verdict.hidden = true; verdict.textContent = ""; }
|
||||
var qwhy = q.querySelector(".quiz-why-q");
|
||||
if (qwhy) qwhy.hidden = true;
|
||||
}
|
||||
var quiz = opt.closest(".quiz");
|
||||
if (quiz) {
|
||||
var score = quiz.querySelector(".quiz-score");
|
||||
if (score) score.textContent = "";
|
||||
}
|
||||
});
|
||||
})();
|
||||
Reference in new issue
Block a user