FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Maintain separate registries for clients and servers connections · Issue #30 · epics-base/epicsCoreJava · GitHub

Repository navigation

Maintain separate registries for clients and servers connections #30

Description

@shroffk opened this issue on Sep 12, 2017:

@mdavidsaver

@mdavidsaver commented on Sep 12, 2017:

https://github.com/epics-base/pvAccessCPP/blob/master/src/client/pv/pvAccess.h#L1322

What is being referred are replacement of the one singleton ChannelProviderRegistry with two access through: ChannelProviderRegistry::clients() and ChannelProviderRegistry::servers().

As I think about it, there was a related change to ChannelProviderRegistry to allow providers to be created with a specific Configuration.

https://github.com/epics-base/pvAccessCPP/blob/master/src/server/pv/serverContext.h#L120

Also, servers can now be created directly with ChannelProvider instance(s) instead of going through the registry/factory process. I found this more natural as all existing server providers are really singletons where the factory concept only gets in the way.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL