On Fri, 26 Jan 2018 at 19:22, Tim Bain <tb...@alumni.duke.edu> wrote:
> > 5.x can also do in-memory-till-full-then-spool-to-disk when using > non-persistent messages (which go to the memory store and then to the temp > store if the memory store is full). > That’s useful info thanks. But non persistent means that the broker will throw away the messages on a reboot? Which wouldn’t be good for me. I can lose a small window of data, but if the wan disconnects for a while and then the machine reboots I need to keep most of the data. >
