Closed funkydonkey123 closed 9 years ago
The saved messages are just in memory. To be possible restore them after a restart we should save the messages on a persistent repository. I don't think this should be a work for the module. Since you can publish the messages again or use the reload instead of restart.
What if server has to restart or nginx needs a restart? In that case all the message are gone. Now I have a use case where it is important to always see part of the latest conversation on that channel even if the last message is several days old. So maybe a persistent storage would be great. Is this something you might integrate or can this be achieved somehow differently (queue the input and write them to mysql database one after another?)
The messages should be stored on the server that will then ping nginx-push-stream-module to publish them so that responsibility should not be a part of this module at all.
@wandenberg I think this can be closed, right?
For some reasons people might have to restart nginx. Currently I see no way to restore the saved messages and channels from before nginx restarted. Maybe this one would be very important for others as well?