Reduce overhead of ASIOMessagingPort resolver service

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Networking
    • None
    • Service Arch
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Right now every ASIOMessagingPort runs its own resolver, which creates background threads. Perhaps we need a persistent resolver service that runs on its own service?

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Matt Cotter (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: