Session이 API token 검증 뒤 Player Actor를 얻어 현재 STREAM session에 bind한다
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Semantic radar needs more MAP space.
자기 메시지와 bind 순서
• 원문 Session→Session 자기 메시지 'Bind current STREAM session'은 archify sequence가 자기 메시지를 지원하지 않아 AuthenticateRes 반환 라벨에 합쳤다. 실제 순서: ActorRef 수신 → 현재 STREAM session에 bind → AuthenticateRes 반환.
• 인증 성공 시 Session은 전역 ActorId와 stable actor type으로 Player Actor를 GetOrCreate한 뒤, Framework가 반환한 ActorRef를 현재 stream session에 bind한다.
원문 Note — binding route
• 원문 Note(Session~Play): AuthenticateRes 반환 뒤의 game packet은 저장된 binding route로 Actor에 relay된다.
• Session은 physical Play endpoint나 NodeRid를 저장하지 않는다. Actor가 계획된 relocation으로 이동하면 Framework가 binding route를 갱신한다.