Added course's notes

This commit is contained in:
MatsuneMikuroi committed 2026-09-25 13:33:30 +02:00
1 parent e07993262c
commit dcd2c072ae
191 files changed
+42866 -12

No files matched your search

+114 -5
View File
@@ -1,9 +1,9 @@
# Conversation Log — Part II — Cross the Process Boundary · Steps 11–18 (turns 29–)
# Conversation Log — Part II — Cross the Process Boundary · Steps 11–18 (turns 29–44)
<!-- nav -->
> [⬅ Previous: Part I](01-part-I.md) · [Index](../conv.md) · Next: *(not started yet)* ➡
> [⬅ Previous: Part I](01-part-I.md) · [Index](../conv.md) · [Next: Part III ➡](03-part-III.md)
>
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · **Part II**
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · **Part II** · [Part III](03-part-III.md)
<!-- /nav -->
---
@@ -388,11 +388,120 @@ Back to the milestone check before Part III: in Step 8 the topology lived in lin
- Viewed the 4 files in `03-static-filesystem/messageBoard/` before committing: plain-text `TEXT` messages from the Step 18 run (`Hello World` and `Uryyb Jbeyq`, with timestamps). Nothing sensitive.
- Logged this turn, then committed `messageBoard/` together with this log update. Not pushed (only a commit was requested).
- Result: commit `e079932` "Keep Step 18 message board as a record of the filesystem run" (4 `.msg` files + log). `main` is 1 commit ahead of `origin/main`.
## [41] Tutor — reply
Committed as `e079932`: the 4 message files from your Step 18 run, plus the log. Not pushed. `main` is 1 commit ahead of `origin/main`, so tell me when you want it pushed.
Heads-up for later: the README resets the board with `rm -rf messageBoard` before some runs. Because these files are now committed, that command will remove them from disk but not from git history. `git status` will then show them as deleted, and we'll decide at that point whether to record the deletion.
Back to the check before Part III: in Step 8 the topology lived in lines 79–85 of `main()`. In the five-terminal version, where does it live now, and who knows it?
**Progress record**
- Current step: end of Part II (check pending)
- Last observed result: `messageBoard/` committed (`e079932`, unpushed)
- Unresolved problem: none
- Next action: student says where the topology lives in the 5-process version; then Part III
---
## [42] Student
> you can push, then i'll start PIII
## [42] Tutor — actions taken
- `git push origin main` → `c5c86e9..e079932 main -> main`. `main` matches `origin/main`. This log update stays uncommitted, as usual.
- Read README lines 1212–1291 (Part III start: Step 19 "One Filesystem Is Not Yet Very Distributed", Step 20 "What Syncthing Is Doing for Us", start of Step 21).
- Read-only check: `syncthing` is **not installed** (`command -v syncthing` found nothing). Package `syncthing` 2.1.5-1 is available in Arch's `extra` repo.
- Schedule check: today is 22 Sep 2026. Part III falls in the inferred Parts II–VIII bucket, due by 29 Sep 2026. On time, no lecture.
## [42] Tutor — reply
Pushed: `c5c86e9..e079932 main -> main`.
## Part III — Make It Actually Distributed
**Schedule:** Part III is in the same bucket as Parts II–VIII, inferred due by **29 Sep 2026**. Today is 22 Sep, so you're on time.
The Part II check (where the topology lives in the five-terminal version) is still open. Answer it whenever you like. It comes back naturally at Step 27, "What Does Our Mediator Actually Contribute?".
**Steps 19–20 — One Filesystem Is Not Yet Very Distributed / What Syncthing Is Doing for Us**
**Goal:** go from five processes on *one* computer to processes on *several* computers, still talking through files.
**Do:** read README lines 1212–1286.
**Tell me:**
1. In your own words: why does the README insist Syncthing is **not** a message broker, even though our messages will travel through it?
2. A practical prerequisite for Step 21 onward: Syncthing isn't installed on this machine (`syncthing` 2.1.5 is in Arch's `extra` repo), and the steps need **at least two computers**. What machines can you use (a second PC, a laptop, a classmate's machine, a VM)? Don't install anything yet; just tell me what you have.
**Progress record**
- Current step: 19–20 (Part III)
- Last observed result: pushed `e079932`; Syncthing not installed (observed)
- Unresolved problem: Part II topology check still open (parked until Step 27 or whenever); machine setup for Syncthing unknown
- Next action: student reads Steps 19–20, explains why Syncthing isn't a broker, and says what machines are available
---
## [43] Student
> Sorry, forgot PII last question, each terminal make live a part (t1 the consoleIn, t2 the link between consoleIn and rot13, t3 rot13, t4 the link between rot13 and consoleOut, t5 consoleOut
## [43] Tutor — actions taken
- None. Compared the answer with `Mediator.java` (generic: route only from `arguments[0]`/`arguments[1]`) and the Step 18 commands. Logged here, in the Part II file, because the answer is about Part II.
## [43] Tutor — reply
No problem. ✅ The mapping is right: T1 ConsoleIn, T2 link ConsoleIn → ROT13, T3 ROT13, T4 link ROT13 → ConsoleOut, T5 ConsoleOut.
That answers *which process does what*. The question was also *where the topology lives and who knows it*. One pointer: open `Mediator.java`. Is `consoleIn/outbox → rot13/inbox` written anywhere in it, or in any other `.java` file? If not, where is that route actually written down, and who wrote it?
One line is enough. Answer it together with the two Part III questions (why Syncthing isn't a broker, and which machines you can use).
**Progress record**
- Current step: 19–20 (Part III); Part II check partly answered
- Last observed result: student mapped the five terminals to their roles correctly
- Unresolved problem: "where the topology lives / who knows it" not yet answered; machines for Syncthing unknown
- Next action: student says where the route is written and who wrote it, plus the Step 19–20 answers
---
## [44] Student
> no, it is written by hand when running Mediator.java <from> <to>
## [44] Tutor — actions taken
- None.
## [44] Tutor — reply
✅ Exactly. No `.java` file contains the route any more. It exists only in the commands **you** typed in Terminals 2 and 4. So the one who knows the topology is **the person starting the processes**.
That completes the arc since Step 1:
- **Step 1:** topology inside the capability code (`IO.println(rot13(text))`).
- **Step 8:** topology in `main()`, lines 79–85, as mailbox-name pairs.
- **Step 18:** topology outside all code, in the operator's command lines.
Each time it moved *away* from the capabilities. It never disappeared. (Bookmark: Step 27 has a subsection titled "Let an Orchestrator Supply the Topology".)
**Part II check done.** Still open, for Part III:
1. Why is Syncthing **not** a message broker, even though messages travel through it?
2. Which machines can you use for Syncthing?
**Progress record**
- Current step: 19–20 (Part III)
- Last observed result: Part II check done (topology lives in the hand-typed `Mediator.java <from> <to>` commands; the operator knows it)
- Unresolved problem: machines for Syncthing unknown
- Next action: student answers the two Step 19–20 questions
---
<!-- nav -->
> [⬅ Previous: Part I](01-part-I.md) · [Index](../conv.md) · Next: *(not started yet)* ➡
> [⬅ Previous: Part I](01-part-I.md) · [Index](../conv.md) · [Next: Part III ➡](03-part-III.md)
>
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · **Part II**
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · **Part II** · [Part III](03-part-III.md)
<!-- /nav -->