How ygjh/airshit works
Project Type and Purpose
• Project type: Desktop P2P LAN file-transfer tool (Java Swing GUI + networking).
• Purpose: Discover peers via UDP multicast, then perform direct TCP file transfers (single/multi-file or folder) with chunking and parallel threads.
File Structure
• Top-level artifacts:
– pom.xml / dependency-reduced-pom.xml: Maven build and packaging
– src/main/java/AirShit: Contains all application code, organized by layers
• Key packages in src/main/java/AirShit:
– ui/ ← Swing panels, dialogs, renderers
– (root) ← Main.java, Client.java, TransferCallback.java
– Network Layer← FileReceiver.java, FileSender.java, ReceiverOptimized.java, SendFileOptimized.java
– File Processing← TarCompressor.java, TarExtractor.java, ChunkInfo.java
– Utilities ← FolderSelector.java, GenerateTestFolder.java, NoFileSelectedException.java
README Insights
• Four logical layers are described:
1) GUI Layer (Swing + small JavaFX adapter)
2) Network Layer (UDP multicast discovery + TCP P2P transfer)
3) File Processing Layer (TAR compression, chunking, parallel threads)
4) Utilities Layer (file selectors, test data gen)
• Main features: automatic discovery, heartbeat, chunked multi-thread transfer, progress callbacks.
Defining the Main Components (to be shown
A. GUI Layer
– Entry point: Main.java
– SendFileGUI + panels under ui/: ClientPanel (peer list), FileSelectionPanel, SendControlPanel, ReceiveProgressPanel, LogPanel
– FXFileChooserAdapter for native file chooser integration
B. Network Layer
– Discovery service (Client.java): uses UDP Multicast on 239.255.42.99:50000 for HELLO/HEARTBEAT
– Transfer service:
• FileSender / SendFileOptimized: establishes TCP sockets to chosen peer, orchestrates chunked send
• FileReceiver / ReceiverOptimized: TCP server socket, receives metadata, chunks, and reconstructs file
– TransferCallback: interface for reporting progress & status back to GUI
C. File Processing Layer
– TarCompressor / TarExtractor: package/unpackage multi-file folder payloads
– ChunkInfo: metadata about file chunks (offset, size)
D. Utilities Layer
– FolderSelector: GUI wrapper for folder selection
– GenerateTestFolder: utility to create dummy payloads
– NoFileSelectedException: validation
E. External Dependencies / Systems
– Local LAN: handles UDP multicast and TCP connectivity
– File system: read/write source/destination files
Relationships & Data Flows
• At startup (Main → Client): GUI subscribes to Client’s peer-discovery events → displays in ClientPanel
• User selects file/folder (FileSelectionPanel → FolderSelector / FileChooserDialog)
• User clicks “Send” (SendControlPanel → triggers SendFileOptimized)
– SendFileOptimized uses TarCompressor (if folder) → divides into ChunkInfo objects → spins up multiple FileSender threads (based on CPU cores) → streams chunks over TCP → TransferCallback updates ReceiveProgressPanel & LogPanel
• On receiver side: Client automatically spawns FileReceiver threads → writes chunks to disk via TarExtractor (if needed) → acknowledges segments → UI progress updated via TransferCallback
Architectural Patterns & Design Principles
• Layered architecture (GUI ↔ Network ↔ Processing ↔ Utilities)
• Event-driven callbacks (TransferCallback) for decoupling network logic from UI
• Strategy for file chunking and thread-pool parallelism (scalable throughput)
• Use of UDP multicast for decentralized peer discovery (no central server)
• Modular packaging (separate Java packages for each layer)
Essential Elements
• Precise component names (e.g., SendFileOptimized, TarCompressor, Client)
• External systems and protocols clearly annotated (LAN, UDP multicast address, TCP ports)
• Event-driven interactions (heartbeats, callbacks)