fix(fls): Gnutella's peer limit is random in Java, not a default
PeerToPeerAnwendung's constructor rolls its peer limit (3, 4 or 5). The
getter defaults measured it once each run — 4, then 5 — and c48d15d
committed 5 as a default. GetterDefaults now constructs every class 64
times and writes a value that varies as {"random": [...]}; the decoder
answers a reference to it as unresolved, and the topology layer reports
a peer limit the file does not set as null.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -11,7 +11,13 @@
|
||||
"JSidebarButton#iconTextGap": 4,
|
||||
"JSidebarButton#verticalTextPosition": 3,
|
||||
"Notebook#maxLayerOfOperation": 4,
|
||||
"PeerToPeerAnwendung#maxTeilnehmerZahl": 5,
|
||||
"PeerToPeerAnwendung#maxTeilnehmerZahl": {
|
||||
"random": [
|
||||
"3",
|
||||
"4",
|
||||
"5"
|
||||
]
|
||||
},
|
||||
"RIPServer#port": 520,
|
||||
"Rechner#maxLayerOfOperation": 4,
|
||||
"ServerBaustein#aktiv": false,
|
||||
|
||||
Reference in New Issue
Block a user