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
..
assets	new versions of dicts with checksums and descriptions	2012-09-08 10:08:39 -07:00
jni	Fix occasional infinite loop of devices sending and receiving the same	2012-11-13 21:25:03 -08:00
libs	merge in changes from the -gcm directory: GCM will be a feature of the	2012-11-02 05:35:31 -07:00
res	up version strings and code	2012-11-08 19:49:45 -08:00
src/org/eehouse/android/xw4	Fix occasional infinite loop of devices sending and receiving the same	2012-11-13 21:25:03 -08:00
.gitignore	ignore new obj dir	2012-01-03 18:27:15 -08:00
AndroidManifest.xml	up version strings and code	2012-11-08 19:49:45 -08:00
build.xml	merge in changes from the -gcm directory: GCM will be a feature of the	2012-11-02 05:35:31 -07:00
build_unchecked.xml	version of build.xml modified to pass -xline to javac. For future use...	2010-11-05 05:06:04 -07:00
project.properties	back to building for android-7	2012-05-30 21:23:53 -07:00