How nicegram/tdlib-ios works
Main Components
a. Core Components:
• TDJsonClient: Interface layer to tdlib's C++ API
• Coordinator: Main orchestrator handling requests and responses
• Stream: Custom implementation for data streaming
• Event System: Handles various events and updates
b. Generated Components:
• API Models (Generated from td_api.tl)
• Function Definitions
• Type Definitions
Architecture Layers
[iOS Application Layer]
• ↕️
[TDLib-iOS Wrapper Layer]
• Coordinator
• Stream System
• Event Handling
• ↕️
[JSON Interface Layer]
• TDJsonClient
• ↕️
[Native tdlib Layer]
Key Interactions to Highlight
a. Authentication Flow:
Coordinator → AuthorizationState Stream → Application
• ↓
TDJsonClient → tdlib → Telegram Servers
b. Request/Response Flow:
Application → Coordinator.send(TDFunction)
• ↓
TDJsonClient (JSON conversion)
• ↓
tdlib → Telegram Servers
• ↓
Response → Promise<Result>
Implementation Details
a. Component Relationships:
• How Coordinator manages TDJsonClient
• Stream subscription system
• Demonstrate Promise-based async operations
b. Data Flow Markers:
External Dependencies
• Integration with TDJSON framework
• PromiseKit dependency
• Telegram API connection points
Implementation Notes
Annotations for:
• Generated code components
• Async operations
• Stream subscription points
• Error handling paths
The separation between native tdlib and Swift interface
• How authentication flows work
• How requests are processed
• How events are streamed
• How the generated code integrates