Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-3247

EndpointDiagnostics.State is not implemented as per the RFC



    • Improvement
    • Resolution: Unresolved
    • Minor
    • backlog-3.0
    • 3.3.3
    • library
    • None
    • 1
    • SDK30, SDK32, SDK37, SDK41


      Previous Title: EndpointDiagnostics.State is always "new" for non-KV services. It was found that this is no longer the case.

      When generating a DiagnosticsReport the EndpointDiagnostics.State is always "new" for non-KV service no matter their state:

      • The problem is that there is no way of knowing the state of the HTTP services because the connectivity aspects are handled by the .NET HTTP Client API AFAIK. This needs to be further investigated and if the state cannot be ascertained, then it should be documented as not cause confusion.
      • The state "New" is not valid per the RFC, it should be one of:

         Disconnected, // the endpoint socket is not reachable
          Connecting, // currently connecting (includes auth,...)
          Connected, // connected and ready
          Disconnecting, // disconnecting (after being connected)



      Acceptance Criteria


      EndpointDiagnostics.State should represent the HTTP status of the endpoint/service using one of the following values {Disconnected, Connecting, Connected, Disconnecting}.

      If possible, pull status from the .NET HTTP client. If not, assume a logical status based on SDK code execution (e.g. If a service can be accessed without throwing exceptions, it is safe to assume the service is connected).


        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.



              emilien.bevierre Emilien Bevierre
              jmorris Jeff Morris
              0 Vote for this issue
              2 Start watching this issue



                Gerrit Reviews

                  There are no open Gerrit changes