Reevaluate BSON 'anchor' logic in IDL after BSON API improvements

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Programmability
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      Based on both the documentation and the code, I suspect IDL is doing deep copies of BSON objects more than we'd really like. Once we have an API that makes tracking BSON lifetimes easier, we should fix that.

            Assignee:
            Unassigned
            Reporter:
            Ronald Steinke
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: