aviadavretz / net-project Goto Github PK

Sometimes, a “rough” exit from a program (e.g.,
ctrl-c) does not properly free up a port

Eventually (after a few minutes), the port will be
freed

To reduce the likelihood of this problem, include
the following code:

#include <signal.h>

void cleanExit(){exit(0);}

in socket code:

signal(SIGTERM, cleanExit);

signal(SIGINT, cleanExit);

When creating a session, server should send address & port to the requesting user, so that the user can open a UDP socket (Other user should be listening for connections 24/7 as long as he isn't in a session/room)

OPENING a room or JOINING it? Isn't it ok to join a room while in session/other room?

Straight from the menachi:
"user can be connected to only to one other user or chat room at a time, calling o or or commands will disconnect other open session."

How we gunna fix dat shyt?!

FUUUUUUU

How dafuq we gunna fix dat

Examples:

• Other user closes the Session in which the user is in.
• Other user closes the Room in which the user is in.
• Server shuts down.

Server should inform the user about these changes in his status.

Stop playing with yourself!

Tried to fix it by separating the "delete socket" from the "stop thread", but it aint workin :(

Server has to send the client some pretty nasty lists yo.
Example: List all users from client

The clients will then be disconnected.

bool UserCredentialsManager::signUp(string username, string password)
{
// TODO: Aviad, why is this here?
if (validateUserCredentials(username, password))
{
return false;
}

// Sign up
return writeUserCredentialsToFile(username, password);

}

When a user enters a chat-room, the server sends him a list of all the addresses inside the room.
He then opens a UDP connection for each one.
Also, the server has to update the other users and tell them the user has joined the room. (Users inside rooms listen 24/7 too?)