Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintain separate registries for clients and servers connections #11

Closed
shroffk opened this issue Sep 12, 2017 · 3 comments
Closed

Maintain separate registries for clients and servers connections #11

shroffk opened this issue Sep 12, 2017 · 3 comments

Comments

@shroffk
Copy link
Contributor

shroffk commented Sep 12, 2017

@mdavidsaver

@mdavidsaver
Copy link

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().

@mdavidsaver
Copy link

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.

@ralphlange
Copy link
Contributor

Copied to its new home.
Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants