The client could send a string longer than 2000 bytes, which would look unterminated.The client could not send null terminated data.While( (read_size = recv(sock, client_message, 2000, 0)) > 0 ) This code in the server assumes that the client will send null terminated data: //Receive a message from client If( send(sock, message, strlen(message), 0) < 0) Printf( 'Type 'q' to end the session: ') If (connect(sock, (struct sockaddr *)&server, sizeof(server)) < 0) Sock = socket(AF_INET, SOCK_STREAM, 0) Write(sock, client_message, strlen(client_message)) If( bind(socket_desc,(struct sockaddr *)&server, sizeof(server)) 0 ) Socket_desc = socket(AF_INET, SOCK_STREAM, 0) Int socket_desc, client_sock, c, *new_sock #include //for threading, link with lpthread But is this really a fool-proof solution? Will this code be able to handle 100's of clients and know about their statuses? I tried with around 10-20 terminals of client and it worked perfectly.Ĭan anyone review my code let me know the errors/ any modifications. So I gave it a thought and somehow managed to use threads to satisfy their requirement partially (code still under development). The first time client gets registered in the server succesfully, they are not able to track about its active execution state on later stages. When the software crashes, Server should get information and the connection should be terminated, freeing any other id's associated with each connected client.Īs of now, they are not able to identify whether client side software has really crashed or is still running.Their Client (Software running on client machine) has some bugs which makes it to crash sometimes.

My Server has to run 24*7*365 for multiple clients at the same time (concurrency).This is my first network programming codes writing for a client who has the following requirement:

Client server c