well, I don't know the answer to the first question but I probably found out the answer for the seconf one. the reason why the program got crazy is that since it's multi threading there's a situation...
my client server application can work in two modes:
1) one direction - only client sends msgs to server
2) two directions - server gives 'answers' to client.
I have a problem that I don't know its source. I got a client - server application (one client only) over TCP. I use berkley socket architecture (i.e. select). I log every msg ID that each...