How luisnguyen1/dappmeeting works
Project Type & Purpose
• The project is a decentralized meeting application that combines blockchain (via smart contracts) and WebRTC for secure and private video conferencing.
• The primary purpose is to manage meeting rooms, authenticate participants using smart contracts, and provide a real-time communication interface using WebRTC, with some advanced frontend effects (like background blur and face mask filters).
Key Components Identified
a. Smart Contract:
• Located in the "bin/smartconstract" directory and further documented under "documents/SmartConstract.md".
• Handles room management, participant authentication, and event propagation.
b. Backend:
• Found in the "Backend" directory, with Go language files (e.g., main.go, MyContract.go, EventHandler.go).
• Acts as the bridge between blockchain events and WebRTC sessions. It also integrates with Cloudflare services for handling media sessions (as indicated by cloudflareService.go and integration details in "documents/Backend.md").
c. Frontend:
• The "frontend" directory contains HTML pages, JavaScript files, CSS, and assets.
• It supplies the user interface and manages interactions with both the smart contract (via blockchain calls) and WebRTC (for media streaming and additional effects).
d. External Services:
• Blockchain network (hosting the deployed smart contract).
• Cloudflare (used for media handling and signaling for WebRTC sessions).
Relationships & Interactions
• The Frontend interacts with:
• The smart contract (for room creation, joining meetings, and verifying participants) via blockchain connection.
• The Backend API to facilitate WebRTC session setup and real-time events.
• The Backend:
• Listens to events from the smart contract.
• Manages interactions with Cloudflare for media transmission and session management.
• Acts as the communication hub between blockchain events and frontend notifications.
• The Smart Contract:
• Serves as a decentralized authentication and room management service, providing a secure mechanism to manage meeting parameters and participant data.
Architectural Patterns & Design Principles
• Separation of Concerns: The project clearly divides responsibilities between the frontend (user experience), backend (logic and integration), and smart contract (decentralized authentication and state management).
• Modular Architecture: Different directories (Backend, frontend, bin, documents) indicate a modular design where each component is independently maintainable.
• Event-Driven Communication: The backend’s event listener and contract event handling illustrate an event-driven model to propagate changes from the blockchain to the application.
• Use of Industry Standards: Go for backend processing, JavaScript/HTML/CSS for frontend, and smart contracts for blockchain integration.