Modify AsyncDBClient/NetworkInterfaceTL to allow Fire and Forget

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Service Arch 2020-02-10, Service Arch 2020-02-24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The simplest form of this involves adding a fireAndForget flag to the RemoteCommandRequest. Then, in the AsyncDBClient, we set the moreToCome flag on the OpMsgRequest and skip the _waitForResponse continuation and return either Status::OK or the error on an actual write(2) socket failure.

            Assignee:
            Cheahuychou Mao
            Reporter:
            Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: