ACK with multiserver

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf ACK with multiserver

  • Creator
    Topic
  • #48164
    Mark Perschbacher
    Participant

      I just loaded the multiserver option, and the tech that sent the license keys suggested making the following change to our ACK proc:

      If you have any procs generating acknowledgements, they will need to be modified to return the CONNID key that comes in with the inbound message.

    Viewing 0 reply threads
    • Author
      Replies
      • #57883
        Charlie Bursell
        Participant

          Your instructions are incomplete.

          Assume the incoming message handle is $mh

          set ackmh [msgcreate -type reply]

          # ADD this statement

          msgmetaset $ackmh DRIVERCTL [msgmetaget $mh DRIVERCTL]

          The rest of your ACK proc does not change.

          FWIW, after adding the above statement, you ACK proc will work just as well for MultiServer and non-MultiServer connections.  No need to have a separate proc.

      Viewing 0 reply threads
      • The forum ‘Cloverleaf’ is closed to new topics and replies.