publish before serving?

[jcw]

Q: Is it possible to publish topics to the server before it starts serving network requests?

This might make it possible to implement persistent retains as a separate process: i.e. log all retained messages to file or some database via a listener subscribed to "#", then on startup have the server go through the saved data and "pre-publish" them as a way to prime the in-memory cache of SurgeMQ.

-jcw

[ankoh]

Right now the retained messages are stored in a Topic-Trie.
So they are just as persistent as any other message in the broker (that is in-memory-only atm).
I don't see the point in implementing persistency for retained messages when everything else is still in-memory.
(A solution to the broker-wide persistency problem most probably brings in the retained message persistency)

[jcw]

So if I understand it correctly, I can call func (*Server) Publish on the server between the creation of that Server object and the call to func (*Server) ListenAndServe? This would allow pre-loading retained messages before the first client has a chance to connect, which is exactly what I'm after.

[ankoh]

@jcw you need to tag me if you want me to read that in time. ;)

In theory - yes.
ListenAndServe is only responsible for instantiating new sessions for incoming TCP connections.
But I rewrote that part completely so I cannot assure you that it will work our of the box.