Social-Chat-App GitHub Details, Stars and Alternatives | OpenRepoFinder
DangHuuLong / repository
Social-Chat-App
A JavaFX desktop social chat application built on a custom TCP socket protocol, featuring real-time messaging, file transfer, group chat, LAN voice/video calling, and AI-powered smart reply suggestions.
A transparent discovery signal based on current public GitHub metadata.
Recent activity35% weight
52
Community adoption25% weight
0
Maintenance state20% weight
100
License clarity10% weight
0
Project information10% weight
75
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
README preview
💬 Social Chat App
A JavaFX desktop social chat application built on a custom TCP socket protocol, with real-time messaging, file transfer, group chat, LAN voice/video calling, and AI-powered smart reply suggestions.
Social Chat App is a Java desktop application implementing a full client-server chat platform. The client and server communicate over TCP sockets using a custom binary frame protocol. The application is built with JavaFX for the UI, MySQL for persistence, and supports a broad set of messaging, file sharing, group chat, and calling features.
The project is structured as a single repository containing the client, server, and a shared common layer used by both sides.
The client connects to the server at 127.0.0.1:5000 via ClientConnection. After authentication, the HomeController initializes three sub-controllers: LeftController (sidebar and user list), MidController (chat area and message logic), and RightController (media/info panel). Specialized handlers under the controller layer manage calls, file transfers, voice recording, media playback, search, and session management.
🖧 Server Side
ServerMain opens a TCP server socket on port 5000 and spawns a ClientHandler thread for each connected client. The server handles message routing, offline queuing, file storage/retrieval, group management, and call signaling delegation via CallRouter. DAO classes manage all MySQL interactions. MessageService handles deletion workflows.
🔗 Shared Protocol / Model Layer
Both sides share the common package. Frame is the base unit of communication, and FrameIO handles serialization and deserialization. MessageType defines all protocol operations. Shared model classes (User, Message, GroupMessage, Group, FileResource) ensure type consistency across the client-server boundary.
💬 Messaging Flow
Client A types message
└─► MidController → MessageHandler
└─► ClientConnection → Frame(SEND_MESSAGE) → Server
└─► ClientHandler → MessageDAO (persist)
└─► Frame(RECEIVE_MESSAGE) → Client B (if online)
└─► Queue (if Client B offline → deliver on reconnect)
Offline messages are queued on the server and delivered when the recipient reconnects.
Smart reply: after storing the message, the server calls http://localhost:8000/smart-reply and forwards suggestions to the recipient if the request succeeds.
📁 File & Media Flow
Client A selects file
└─► FileHandler → FILE_META frame (filename, size, type)
└─► FILE_CHUNK frames × N (64 KB each, max 25 MB)
└─► Server stores file → notifies Client B
└─► Client B downloads on demand
Files are classified as image, audio, video, or document.
Voice messages are recorded locally (max 30 seconds), previewed, then sent as audio chunks.
Media playback on the client uses JavaFX Media APIs. An InMemoryMediaServer exposes in-memory audio/video as local HTTP URLs to support JavaFX's media player.
👥 Group Chat Flow
A user creates a group and adds members.
Group messages follow the same Frame-based flow, routed to all active members by the server.
Members can be added or removed by authorized users.
If the group owner leaves and other members remain, ownership is reassigned automatically.
The group can be deleted by the owner.
📞 Call Flow
Caller sends CALL_INVITE frame
└─► Server (CallRouter) → forwards to Callee
├─► Callee accepts → CALL_ACCEPT → LAN media session opens
├─► Callee rejects → CALL_REJECT
├─► Callee busy → CALL_BUSY
└─► Caller cancels → CALL_CANCEL
During call:
LanAudioSession — PCM audio streamed over direct socket
LanVideoSession — JPEG frames from webcam streamed over direct socket
Toggle mic / camera supported
Dedicated VideoCall.fxml window with local + remote views
Either party sends CALL_END → session closes
⚠️ The calling implementation is LAN-oriented. It relies on direct socket connections between peers and is not designed for NAT traversal or internet-grade calling.
🗄️ Database Summary
Database name: socialchatapp
JDBC connection via MySQL driver
Users — id, name, email, hashed password (BCrypt), avatar, online status, last seen
Messages — direct messages with sender, receiver, content, timestamp, edit/delete state
