Eric House 2629c07256 Address problem with devids (e.g. GCM): until now when you got a new ... devid you tossed your relayID and reregistered. Which meant any existing messages meant for your relayID were orphaned, and any open games didn't know who they belonged to until you reconnected to them with your new relayID. So: modify the UDP protocol (though not on Android yet) to include both relayID and devid with registration, with one or the other an empty string if not present or not changed from earlier. I can't fix existing clients that are dropping their relayIDs, but when one does a re-connect without a relayID I can look it up from the existing game record, then reuse it rather than issue a new one. Better than nothing -- and that protocol will be obsolete soon anyway.		2013-09-14 21:06:14 -07:00
..
android	turn chat back on -- and make it configurable via a single property in	2013-09-11 22:18:00 -07:00
common	drop duplicate packet rather than asserting	2013-09-11 07:30:12 -07:00
dawg	add DICTNOTE	2013-05-21 06:58:53 -07:00
debian	ignore debian build files	2012-01-04 18:11:29 -08:00
linux	Address problem with devids (e.g. GCM): until now when you got a new	2013-09-14 21:06:14 -07:00
relay	Address problem with devids (e.g. GCM): until now when you got a new	2013-09-14 21:06:14 -07: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	list java files first so their methods, which tend to be more	2013-07-11 19:56:37 -07:00