How robertinglin/vertstack works
Main Components
a) Core Framework Components:
• VertStack Server (Central Hub)
• WebSocket Manager
• Template Engine
• Static File Server
• Proxy Handler
• URL Rewriter
• Session Manager
b) Module Architecture:
• Module Container
• Client-Side Runtime
• Server-Side Runtime
• Message Bus System
• Client Browser |
• Module 1 | | Module 2 | | Module 3 | | Module N | |
• (iframe-based) | | (iframe-based) | | (iframe-based) | | (iframe-based) | |
• ⇅
• WebSocket Layer |
• ⇅
• VertStack Core Server |
• Session Manager| | Template Engine | | Static Server | | Message Bus | |
• URL Rewriter | | Proxy Handler | | Module Loader | |
• ⇅
• Module Server Instances |
• Module 1 | | Module 2 | | Module 3 | | Module N | |
• Server Runtime | | Server Runtime | | Server Runtime | | Server Runtime | |
Additional Details
• Annotations for key features like automatic iframe resizing
• Session management flow
• Proxy routing mechanisms
• Demonstrate template resolution paths
Implementation Notes
• Maintain consistent spacing and alignment
• Version information
• Notes for scaling considerations
• Document proxy configurations
Key Relationships to Highlight
• WebSocket connections between client modules and server
• Template inheritance and override patterns
• Static file serving paths
• Session management flow
• Cross-module communication patterns
• Proxy routing relationships