DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, verifiedOn, source
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | verifiedOn | source | |
|---|---|---|---|---|---|---|---|---|---|---|
| REFERENCE | messaging-spring-cloud-stream-bridge-f05 | 등록을 받는 컴포넌트는 해제도 제공한다 | runtime-reachability-and-composition | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | reference:messaging-spring-cloud-stream-bridge-f05 |
|
등록을 받는 컴포넌트는 해제도 제공한다
목적
바인딩이 재구성되거나 컨텍스트가 종료될 때 맵이 비워지지 않는다. 오늘은 조립되지 않아 무해하다. 같은 가족의 messaging-transport-spi 는 TransportConsumerRegistration 을 AutoCloseable 로 두어 반대편을 이미 갖췄다.
규칙
-
등록 메서드가 있으면 짝이 되는 해제를 찾는다 SpringCloudStreamConsumerBridge 에 unregister 도 close 도 없다. SpringCloudStreamPublisherBridge 도 마찬가지다.
-
없으면 등록이 프로세스 수명과 같아지는지 확인한다 여기서는 바인딩 재구성이 그 가정을 깬다.
-
unregister(bindingName) 이나 AutoCloseable 중 하나를 둔다 둘 중 어느 쪽이든 해제 시점이 코드에 생긴다.
적용 조건
핸들러·리스너·바인딩을 맵에 담아 두는 모든 등록 컴포넌트.
예외
등록이 애플리케이션 수명과 정확히 같고 재구성 경로가 없으면 대상이 아니다. 이 브리지는 재구성을 전제하는 자리에 있다.
예시
두 클래스의 public 메서드 전수. 확인 방법은 그 목록을 보는 것이다.