How hhubb22/ostinato works
And Represent Main Components
• Client Application (GUI):
– Folder: “client” contains all the user interface components, UI forms (.ui files), and associated logic.
– This layer is responsible for the user interactions (e.g., configuring streams, managing ports, viewing status, etc.).
• Common Libraries and Protocol Implementations:
– Folder: “common” holds numerous protocol definitions (e.g., ARP, ICMP, TCP) and helper functions.
– Represents the code for packet crafting, protocol-specific encoding/decoding, and common utilities shared by both the client and server.
• Server Component:
– Folder: “server” includes modules for packet handling, port/device management, capturing/transmitting packets, and interfacing with the hardware/network stacks.
– Implements the back-end logic and processing to support the client’s configuration and data capture.
• RPC Mechanism:
– Folder: “rpc” indicates that Ostinato has a remote procedure call interface (using protobuf-based modules such as pbrpcchannels, rpcconn, etc.).
– This connects the client and server components to allow remote control and data exchange.
• Additional Tooling and Extensions:
– “extra” and “test” directories house model tests and additional editor components (like QHexEdit) which underline extensibility and testing practices.
Relationships and Data Flow
• The Client interacts with the Server primarily through the RPC layer.
• The Server uses shared “common” libraries to process and generate network packets based on the client's configuration.
• There is a feedback loop from the Server back to the Client (via RPC responses) so that status updates, packet logs, and configuration changes are reflected in the GUI.
• Testing, building, and contribution workflows (reflected via .travis.yml, .github, etc.) could be shown as supporting infrastructure but are less central to runtime architecture.
Architectural Patterns and Technologies
• Separation of Concerns / Modular Architecture:
– The project clearly separates the GUI (front-end), business logic (server), and shared libraries (common protocols) which is a classic layered architecture.
• Use of RPC:
– A dedicated RPC design pattern is adopted to allow remote operations and easy scalability.
• Frameworks and Tools:
– The client uses Qt (presence of .ui files, .qrc, etc.) for building the GUI.
– The server is built to interface with diverse platforms (Windows, Linux, BSD) as suggested by platform-specific files (winhostdevice.cpp, linuxport.cpp).
Final Customization for Ostinato’s Purpose
• Separation of network packet crafting (common library) from the GUI interface (client) and the backend packet processing/transmission (server).
• That the RPC mechanism serves as a critical bridge between frontend and backend.