GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Can you add some kind of an external file structure for unsent messages, so if the problem is in configuration,
those messages can be re-sent when server is restarted with new configuration?
Or maybe an external resend_old.js script, which would drain the unsent queue, using the new config.
Main point: avoid silently dropping messages when sending is a problem.
i like the idea.
however, is this not supported by the callback that currently exists on send?
server.send(headers, function(err, message)
then you can make a resend script that just runs through each message in the file and call send on them one by one
let me know if you had something else in mind or if i misunderstood the request.
indeed, a file makes for a well behaved persistent message store.
will try it and see if the callbacks work as advertised, thanks !