Prerequisites : Introducing threads in socket programming
In the above article, a simple date time server was created which handled multiple user requests at the same time using threading. It explains the basic concepts of threading in network programming. The same concepts can be used with very slight modification to extend the above idea and create a chatting application similar to facebook messenger, whatsapp etc.
The following article covers the implementation of such an application with a detailed explanation, limitations, and their solutions.
In this set, we will discuss Server side programming(Server.java), Client side programming(Client.java) is discussed in Set 2.
Server Side Programming(Server.java)
- Server class : The main server implementation is easy and similar to the previous article. The following points will help understand Server implementation :
- The server runs an infinite loop to keep accepting incoming requests.
- When a request comes, it assigns a new thread to handle the communication part.
- The sever also stores the client name into a vector, to keep a track of connected devices. The vector stores the thread object corresponding to the current request. The helper class uses this vector to find the name of recipient to which message is to be delivered. As this vector holds all the streams, handler class can use it to successfully deliver messages to specific clients.
- Invoke the start() method.
- ClientHandler class : Similar to previous article, we create a helper class for handling various requests. This time, along with the socket and streams, we introduce a name variable. This will hold the name of the client that is connected to the server. The following points will help understand ClientHandler implementation :
Whenever the handler receives any string, it breaks it into the message and recipient part. It uses Stringtokenizer for this purpose with ‘#’ as the delimiter. Here it is assumed that the string is always of the format:
message # recipient
- It then searches for the name of recipient in the connected clients list, stored as a vector in the server. If it finds the recipients name in the clients list, it forwards the message on its output stream with the name of the sender prefixed to the message.
- Whenever the handler receives any string, it breaks it into the message and recipient part. It uses Stringtokenizer for this purpose with ‘#’ as the delimiter. Here it is assumed that the string is always of the format:
New client request received : Socket[addr=/127.0.0.1,port=61818,localport=1234] Creating a new handler for this client... Adding this client to active client list New client request received : Socket[addr=/127.0.0.1,port=61819,localport=1234] Creating a new handler for this client... Adding this client to active client list
Although the above implementation of server manages to handle most of the scenarios, there are some shortcomings in the approach defined above.
- One clear observation from above programs is that if the number of clients grew large, the searching time would increase in the handler class. To avoid this increase, two hash maps can be used. One with name as the key, and index in active list as the value. Another with index as key, and associated handler object as value. This way, we can quickly look up the two hashmaps for matching recipient. It is left to the readers to implement this hack to increase efficiency of the implementation.
- Another thing to notice is that this implementation doesn’t work well when users disconnect from the server. A lot of errors would be thrown because disconnection is not handled in this implementation. It can easily be implemented as in previous basic TCP examples. It is also left for the reader to implement this feature in the program.
There is a huge difference in the client program(Client.java) than the previous articles, so it will be discussed in Set 2 of this series.
Related Article : Multi-threaded chat Application | Set 2
This article is contributed by Rishabh Mahrsee. If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above.
Attention reader! Don’t stop learning now. Get hold of all the important DSA concepts with the DSA Self Paced Course at a student-friendly price and become industry ready.
- Multi-threaded Chat Application in Java | Set 2 (Client Side Programming)
- Creating an Asynchronous Multithreaded chat Application in Java
- A Group chat application in Java
- Creating an Server-Client Application using the DatagramPacket and DatagramSocket classes
- Difference between a Java Application and a Java Applet
- How to run Java RMI Application
- JSF | Java Server Faces
- Establishing the two-way Communication between Server and Client in Java
- Java Implementation of Deffi-Hellman Algorithm between Client and Server
- Java tricks for competitive programming (for Java 8)
- Java Programming Basics
- Socket Programming in Java
- Different Approaches to Concurrent Programming in Java
- Comparison of Java with other programming languages
- Beginning Java programming with Hello World Example
- Fast I/O in Java in Competitive Programming
- Which Java libraries are useful for competitive programming?
- Functional Programming in Java with Examples
- Introducing Threads in Socket Programming in Java
- The complete History of Java Programming Language