Write a Java TCP MultipleClient-Server Program for following scenario. NOTE Server Details are in the above figure Client-Server communicates continuously until the Client send Bye to the Server Use Multithreading for Multiple Clients NOTE : 1 cm = 0.39 inches 1 cm = 0.03 foot 1 cm = 0.01 meter Sample Ouput: Client Server 1 – cm to inches 2 – cm to foot 3 – cm to meter Enter length in cms (int) : 10 Received from Server 3.9 inches 1 – cm to inches 2 – cm to foot 3 – cm to meter Enter length in cms (int) : BYE Received from Server BYE Client DISCONNECTED Server Waiting for the Cline to be Connected… CONECTION ESTABLISHED Received From Client 10 cms Sent to Client 3.9 inches Received From Client BYE Sent to Client BYE HINT : When client choses 1 for cm to inches and enter 10, then the client sends the string 110 to the Server. Where the first char ‘1’ represents the cm to inches and the other 2 chars represents the 10.

TCP MULTIPLEXING AND DEMULTIPLEXING In the scenario below, the left and right TCP clients communicate with a TCP server using TCP sockets. The Python code used to create a single welcoming socket in the server is shown in the figure (the welcoming socket itself is not shown graphically); code is also shown for the client sockets as well. The three sockets shown in server were created as a result of the server accepting connection requests on this welcoming socket from the two clients (one connection from the client on the left, and two connections from the client on the right). mySocket = socket (AF_INET, SOCK_STREAM) mySocket.bind (myaddr, 6189 ); P1 Answer mySocket = socket (AF_INET, SOCK_STREAM) mySocket.bind (myaddr, 5854 ); ♫ transport QUESTION 1 OF 8 network link physical What is the source port # for packet C? www B source port: ? dest port: ? P4 HIGH A source port: ? dest port: ? P5 P6 transport network lirk physical mySocket1 = socket (AF_INET, SOCK_STREAM) mySocket1.bind…

USING JAVA (Java Socket /TCP Programming) Create a chat/messaging application that has the following functionalities/features: Broadcast message (to all users) Private message to only one message (established usernames are stored in an XML file)

How do handler interfaces accommodate the integration of newer protocols or communication standards?