Eric House 259357a818 reduce sending of dead-game mqtt messages ... Two cases dealt with here. First, if my opponent deletes the game when I have an un-ack'd message, I'll keep sending it forever. Fix is to flip a bit in comms in response to a game_gone event so no more sending will happen. (Better than emptying the queue, as it leaves open the possibility of resurrecting the game with code changes later.) Second, if there's a retained message from a dead game I'll keep receiving it until it's replaced, and if the game's dead it never will be. Fix is to add a new api endpoint noSuchGame() to the relay2 server and to call it on receiving a message for which I have no game to deliver it to. The endpoint "unretains" the message so I won't get it again unless it's resent.		2023-11-05 12:01:43 -08:00
..
android	reduce sending of dead-game mqtt messages	2023-11-05 12:01:43 -08:00
common	reduce sending of dead-game mqtt messages	2023-11-05 12:01:43 -08:00
dawg	tweak xwd header output	2023-05-29 16:55:14 -07:00
debian	ignore debian build files	2012-01-04 18:11:29 -08:00
linux	shorten file path in logs	2023-10-29 08:09:37 -07:00
newrelay	beginnings of new relay: shows persistence	2017-11-05 19:24:41 -08:00
relay	add manual message-send to fcm_loop for testing	2020-12-14 08:57:11 -08:00
scripts	more work on script	2014-02-26 07:52:18 -08:00
tests	allow to run multiple games at once	2005-09-14 05:12:07 +00:00
wasm	add git rev to display	2023-05-29 16:55:14 -07:00
Makefile	include all .xml and .java files, but only if they're not named in a .gitignore file in the same directory	2014-03-01 11:44:20 -08:00