Eric House d799b94169 use persist flag and new per-game mqtt topics (too) ... I didn't understand MQTT at all. Per the docs anyway it only keeps a message around if its "persist" flag is set, and then it only keeps the most recent per topic. I expected that when a device connected, messages would be waiting for it, but that's apparently not true (some evidence to the contrary.) But having all games on a device share the same topic means only one message can be waiting. So switch to including gameID in the topic, subscribing to a wildcard topic and sending to a different one per game. For now, for legacy purposes, we'll keep sending to the old per-device topic.		2022-12-16 14:35:22 -08:00
..
android	use persist flag and new per-game mqtt topics (too)	2022-12-16 14:35:22 -08:00
common	use persist flag and new per-game mqtt topics (too)	2022-12-16 14:35:22 -08:00
dawg	add note explaining source	2022-11-04 10:08:24 -07:00
debian	ignore debian build files	2012-01-04 18:11:29 -08:00
linux	use persist flag and new per-game mqtt topics (too)	2022-12-16 14:35:22 -08: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	fix wasm build	2022-04-01 07:51:13 +02: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