akicks wrote: You misunderstood what I was saying, which is a shame.....Now they have put down there phones. Imagine that they are now going to talk to each other without the phone and that the sound can reach. What person A says person B does not hear for 4 full seconds. Similarly what person B says person A does not hear for 4 full seconds. Now, if person A asks person B a question, he won't get an answer for 8 full seconds. (that's lag, and pretty bad lag to!).
Yeah it is a shame ... that you are not taking into account the fact that the server sent an aknowledgement to the client BEFORE the other message. To use you analogy....to be comparable, we have to think that person A can't hear himself talk (he must be married
). because person A can't put messages in sysinfo, only the server can. So here goes using your analogy.
Person A says "I hit INV" .... now sound travels to person B
Person A hears person B say "I just heard you say you hit INV"
Person A hears Person B say "You just got whacked".
Now tell me again, if the "you just got whacked" statement was made by person B before person B made the statement "I just heard you say you hit INV" thru what time warp is one of these messages from B traveling such that the one that was said by B last, arrives at person A 1st ?
The server sent a message saying it recognizes and has logged in the fact that INV was hit. If the server sent a message saying the Mob hit me before that acknowledgement, then why doesn't the hit message arrive before the acknowledgement message ? Both messages are coming from the same place so how did they get out of order ?
How many times have you hit INV 4, 5 even 6 times before it took effect.....it doesn't take effect and it doesn't appear in sysinfo until the server recognizes that INV has been hit. Pushing the button, does not put a message in sysinfo, the server puts the message in sysinfo.
Here's how your anology pans out using the 4 second lag you chose.
0:00 Person hits INV
0.04 Message saying you hit INV arrives at server
0.08 Message arrives back from server acknowledging INV hit and posting that info in sysinfo box
0.09 Message from server says you been hit by mob
Now if it the lag is 4 seconds, working back from when the "you got hit message" arrived, the message must have been sent at 0:05 which is after the server already acknowledged that it knows I hit INV.
Now unless the time for the mile apart yelling at each other takes 4 seconds when you say one thing and more than 4 seconds when you say something esle, the analogy doesn't hold.
Again, this is not my explanation but Nevrax's tech support. By way of explanation, he asked if I ever noticed client side if I typed something in a chat box druing a "Please Wait". It disppears client side from the window you type in but doesn't appear in the appropriate chat box till
after the server has received it and sent it back. You don't see stuff in sysinfo until it's been received by the server and sent back to you....or an 8 second round trip in your analogy.
Again, I am only going by what the TS dude said, he could be right, he could be wrong but given the alternatives, I gotta go with the trained technician's explanation. But what they said was that when two inputs arrive close enough together, they get processed in the same computing input cycle the server processes them out of order (first in last out). It makes sense.
And BTW, two peeps a mile apart would experience a lag of about 4.67 seconds at sea level at 72 degrees F, in dry air.
)
), it happened 3-4 times.