Update SDAM to not request immediate rechecks on network errors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Connectivity
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During the code review phase of CSHARP-3057, we discovered that it seems like we may not following this part of the SDAM spec regarding network errors (as our SDAM implementation predates the spec):

      Clients MUST NOT request an immediate check of the server; since application sockets are used frequently, a network error likely means the server has just become unavailable, so an immediate refresh is likely to get a network error, too.

       

              Assignee:
              Unassigned
              Reporter:
              Vincent Kam (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: