+- Forums - Open Redstone Engineers (https://forum.openredstone.org)
+-- Forum: ORE General (https://forum.openredstone.org/forum-39.html)
+--- Forum: Build Discussion (https://forum.openredstone.org/forum-50.html)
+--- Thread: Time out: These bitches and why they happen (/thread-5718.html)
Time out: These bitches and why they happen - Konstacon - 02-04-2015
We all have been building something then randomly, as if you were kicked by and admin, are kicked from the server giving the message "Timed Out"
I'm doc finap here... explaining why.
How they happen
When you connect to a minecraft server, you send packets to the main server (Which is in mort's basement, along with his many prisoners of war). You always get packets back from the server. When you send packets to a server, you are "requesting" the server. When a request takes too long to complete, you're left with a time out and are disconnected.
For example, in a DDoS, the server spends all it's energy replying to the botnet's request, so that all the other requesters (visitors) are timed out. The server can even burn out from this.
Why they happen
You may be thinking why? (and pauly "fokn wut m8"). This is so the server can complete other requests and not spend all it's time on your's. Therefore it disconnects you for the better of itself, so that the other people don't have slow reply.
In other words... servers are dicks.
your welcome for explaining your rage and sleepless nights over these fuckers.
RE: Time out: These bitches and why they happen - PabloDons - 02-04-2015
(02-04-2015, 02:02 AM)snugglycreeper9 Wrote: Therefore it disconnects you for the better of itself, so that the other people don't have slow reply.
you're overrating server intelligence. servers only do what they're told to do. most don't disconnect some random people for the better of itself. that is HIGHLY undesirable because random performance drops can easily trigger it (in which case the server has disconnected innocent souls for no reason). if you put a timer on it, then everyone else are probably disconnected from a timeout by the time that command is triggered. in which case it is completely and utterly incorrect. servers usually reply to packets in the order it is recieved, if suddenly a large amount of packets are received, the server will try to reply to all of them which would take too long and others waiting in line after it will get a timeout. also if a server runs at maximum performance in a long period of time, this is where server crashes and system burnouts come in that are difficult to explain in detail. most systems trigger something to slow itself down when it overheats so a fire doesn't start.