[2016-04-07 04:09:28 UTC] guys i dont believe it, for my project for the networking thing we were supposed to be assigned a partner (so that we would implement thread based/event based server and client stuff), but THANKFULLY i actually didnt get one, since I have absolutely no idea how to get event based stuff to work in java [2016-04-07 04:10:00 UTC] which means that the ta emailed me saying that i could choose to make either the client or server thread or event based [2016-04-07 04:10:07 UTC] which basically overall means LESS WORK [2016-04-07 17:00:43 UTC] Congrats [2016-04-07 17:00:49 UTC] ! [2016-04-07 20:31:05 UTC] um.. so question about multithreaded programming, currently the way i set is up is that i have a blocking call to receive a packet in the main server loop, and the server then examines the packet to check out what session id, [2016-04-07 20:31:59 UTC] then it calls a method for that currently running session thread, which doesnt block but is in a loop that waits until either its closed or receives a new message, in which case it handles the new message it received (the main server loop sends this) [2016-04-07 20:32:42 UTC] BUT should i instead have each thread handle the main socket and block until it recieves, then that thread checks out if it needs to handle the message or not [2016-04-07 20:33:07 UTC] because im thinking it probably aint safe to have tons of copy of data and sockets around