How aitorblanco03/distribuidos-p1-sockets works
Project type and purpose
• This is a Java-based, console chat application using TCP sockets.
• Purpose: real-time multi-user chat within a LAN, supporting broadcast messaging, per-user blocking, safe disconnect, and thread-based concurrency.
File structure
• Top-level:
• pom.xml, build.xml – Maven and Ant build definitions
• src/main/java/es/ubu/lsi
– client: ChatClient.java / ChatClientImpl.java
– server: ChatServer.java / ChatServerImpl.java
– common: ChatMessage.java, MessageType.java
• src/test/java: AppTest.java
• doc/: Generated Javadoc site
• No database directory; it’s pure in-memory, socket-based.
• Concurrency artifacts: ChatServerImpl uses threads, read/write locks.
README for additional insights
• Three core modules: Server, Client, Message model.
• Server handles incoming connections, broadcasting, block lists, thread safety.
• Client connects to server, spawns threads for input/output, processes commands.
• Messages carry sender, payload, type (broadcast, ban, logout).
Components
a. Main components
1. ChatClient instances (multiple)
• Subcomponents:
• User Input Handler (stdin → ChatMessage)
• Network I/O Handler (socket read/write)
• Command Processor (ban/unban/logout commands)
2. TCP Network (LAN)
3. ChatServer
• Subcomponents:
• Connection Listener (accepts new socket connections)
• ClientHandler Threads (one per client)
• Broadcast Service (forwards messages to all handlers)
• Block Manager (tracks banned/unbanned users)
• ReadWrite Locks (protect shared state)
4. Common Model (shared library)
• ChatMessage, MessageType
b. Relationships & interactions
• Clients open TCP socket to Server → Connection Listener spawns ClientHandler
• ClientHandler receives ChatMessage, passes it to Broadcast Service
• Broadcast Service iterates through active handlers, sending to each unless blocked
• ClientHandler writes message bytes back over socket → Client Network I/O receives and displays
c. Architectural patterns & design principles
• Client-Server pattern over TCP sockets
• Thread-per-connection concurrency model
• Read/Write locks for safe concurrent access to shared lists (clients & block lists)
• Message-based communication using serializable ChatMessage objects
d. Relevant technologies
• Java SE 17+ (java.net.Socket, java.net.ServerSocket, java.util.concurrent)
• Maven & Ant for build/dependency management
• Javadoc for API documentation