• Add a connect callback handler.

    From Rob Swindell@VERT to GitLab note in main/sbbs on Monday, August 21, 2023 10:29:51
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/320#note_3832

    No, that is not a notification telling clients "this server has recycled".

    If I remember correctly, the publishes to the "recycle" topic were necessary to reset the server/services recycle semaphore timestamp upon initial bring-up. Something like that.

    ---
    � Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net
  • From Rick Parrish@VERT to GitLab note in main/sbbs on Monday, August 21, 2023 15:55:40
    https://gitlab.synchro.net/main/sbbs/-/merge_requests/320#note_3833

    Ahh, bad assumption on my part then!

    So in hindsight, maybe these two lines should have stayed in mqtt_startup, since it's only the subscriptions that need to be re-applied in the connect callback when a reconnect occurs:

    mqtt_pub_noval(mqtt, TOPIC_SERVER, "recycle");
    mqtt_pub_noval(mqtt, TOPIC_SERVER, "client");

    I just tested that here, and my Linux build no longer hits a recycle loop even with the Publish QOS set to 1.

    ---
    � Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net