Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-2517

Introduce a retry status code to the server protocol

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.4.10
    • Fix Version/s: 3.5.0
    • Component/s: server
    • Labels:
      None

      Description

      There is no common server code that defines when applications should retry a request. Without such a code, developers are left to (1) write provider specific code (i.e. Neptune retry codes vs JanusServer codes) and/or (2) parse response error messages to determine if retry is needed. If TinkerPop specified a code or code series that signified retry users could easily depend on it in their application logic. We would not look to implement retry logic in the drivers themselves - that would remain a task for application developers. Looking at the current response codes I'd think that we would just add SERVER_ERROR_TEMPORARY 596

      cc/ Divij Vaidya

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                spmallette Stephen Mallette
                Reporter:
                spmallette Stephen Mallette
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: