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
..
scripts	merge in changes from the -gcm directory: GCM will be a feature of the	2012-11-02 05:35:31 -07:00
website	tweak name and reflect new name on website	2012-08-30 19:21:05 -07:00
XWords4	Fix occasional infinite loop of devices sending and receiving the same	2012-11-13 21:25:03 -08:00
XWords4-bt	get rid of NODE_CAN_4. Not change to post-compiled code	2012-08-01 20:29:15 -07:00
XWords4-dbg	add temp menu that gets a phone number and sends an NBS message to it,	2012-03-13 07:51:45 -07:00
XWords4-sms	starting new variant for GCM	2012-10-16 07:41:04 -07:00
.gitignore	ignore dir not on this branch	2012-10-16 08:20:53 -07:00
Application.mk	initial checkin of jni source and build scripts for android port	2010-01-02 19:10:08 +00:00
INSTALL.txt	update instructions for building	2011-11-19 20:05:04 -08:00