You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2021/02/03 12:02:00 UTC

[jira] [Created] (TINKERPOP-2517) Introduce a retry status code to the server protocol

Stephen Mallette created TINKERPOP-2517:
-------------------------------------------

             Summary: Introduce a retry status code to the server protocol
                 Key: TINKERPOP-2517
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2517
             Project: TinkerPop
          Issue Type: Improvement
          Components: server
    Affects Versions: 3.4.10
            Reporter: Stephen Mallette


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.  cc/ [~divijvaidya]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)