Track maxMessageSizeBytes for a connection

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: 0.0.2
    • Component/s: Wire Protocol
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      To satisfy GODRIVER-150 we need to track the maxMessageSizeBytes parameter returned from an isMaster command. When we read a response, we need to check if the messageLength of the header is larger than maxMessageSizeBytes.

      For the first isMaster call, we use 48MB according to DRIVERS-276.

            Assignee:
            Unassigned
            Reporter:
            Kristofer Brandow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: