What is the expected direction for client/pool options?

XMLWordPrintableJSON

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

      The current configuration approach varies:

      • Some configuration options may only be set in the URI; e.g. sockettimeoutms
      • Some configuration options may only be set via code; e.g. SSL options
      • Some configuration options may be set either way: e.g. appname, minimum pool size

      Do you have a sense for which of these models will be more common in the future?

      Do you expect that options for a pool will always remain a superset of the options for a client?

              Assignee:
              Unassigned
              Reporter:
              David Golden
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: