Eric House c4df31892e Fix occasional infinite loop of devices sending and receiving the same ... message over and over when getting updated by GCM. The problem occurred when one device had an un-ACKable initial message still in its queue. I call resendAll a lot, which caused that message to get resent to the other game which then replied without being able to ACK it so it remained to be sent again. This would continue until users moved forward in the game. The fix is to add a backoff timer to resendAll() so that it can't loop. The timer is reset when an ackable and new message is received, meaning there's been a change in what's available to resend. And since users calling resendAll manually expect it to do something, add a force param that ignores the backoff. seems to fix the problem (but needs a lot of testing.)		2012-11-13 21:25:03 -08:00
..
android	Fix occasional infinite loop of devices sending and receiving the same	2012-11-13 21:25:03 -08:00
common	Fix occasional infinite loop of devices sending and receiving the same	2012-11-13 21:25:03 -08:00
dawg	update for newest wordlist	2012-10-31 07:12:10 -07:00
debian	ignore debian build files	2012-01-04 18:11:29 -08:00
linux	Fix occasional infinite loop of devices sending and receiving the same	2012-11-13 21:25:03 -08:00
relay	minor printing tweaks	2012-11-13 07:17:56 -08:00
scripts	remove echoing	2011-09-14 05:45:32 -07:00
tests	allow to run multiple games at once	2005-09-14 05:12:07 +00:00
wince	ignore dicts in main wince dir	2011-12-14 07:37:59 -08:00
Makefile	include java files in TAGS	2010-01-25 02:09:08 +00:00