Unique DaprClient Instance(s) to exist per combination of host, port and config options #349
Description
Describe the proposal
Currently, multiple DaprClient instances get formed, even for same host, port and DaprClientOptions.
Proposal is to cache in some form the combinations of Host, Port and DaprClientOptions, for which DaprClient(s) are getting formed, and return the same instance - if it already exists for the unique combination of host, port and options; Or else, form a new DaprClient instance and store this unique combination in this cache.
Need to check cache (map?) limits and do we want to keep it bounded in some form?