Uploaded image for project: 'Ruby Driver'
  1. Ruby Driver
  2. RUBY-1502

Correctly handle monitoring when duplicating clients

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 2.7.0.rc0
    • Affects Version/s: None
    • Component/s: None
    • None

      Currently when a client is duplicated (via #dup or #with), monitoring is sometimes copied into the new client and sometimes a brand new monitoring is created. In the former case event subscriptions in the new client affect the old client, in the latter case event subscriptions in the old client are not inherited.

      Let's have the event subscriptions be copied so that the new client has subscribers to the original client but changes to the new client do not affect the original client.

            Assignee:
            oleg.pudeyev@mongodb.com Oleg Pudeyev (Inactive)
            Reporter:
            oleg.pudeyev@mongodb.com Oleg Pudeyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: