When a message is to long, or when the server is processing several messages at the same time sometimes they can come divided in two parts, which can lead to undefined behaviour. In order to fix this the parsing should do the following:
[x] Create a vector of commands, which will wait for all the information the user sent, and add it to the vector that should be in the Clients Class. To know the end of a command, the message needs to end in \r\n or \n\r (not sure which one is, need to confirm)
[ ] In socket connection function, it should only allow the user to go check the actions after all commands are added to the vector.
When a message is to long, or when the server is processing several messages at the same time sometimes they can come divided in two parts, which can lead to undefined behaviour. In order to fix this the parsing should do the following:
[x] Create a vector of commands, which will wait for all the information the user sent, and add it to the vector that should be in the Clients Class. To know the end of a command, the message needs to end in \r\n or \n\r (not sure which one is, need to confirm)
[ ] In socket connection function, it should only allow the user to go check the actions after all commands are added to the vector.