Difference between revisions of "V4 Name Server"
From EPICSWIKI
KayKasemir (talk | contribs) m (→Name Server) |
KayKasemir (talk | contribs) m (name server not only for CA) |
||
| Line 3: | Line 3: | ||
=== Name Server === | === Name Server === | ||
What would a name server look like that supports | |||
1) Life channels (ChannelAccess), including channels provided by backup systems in a redundant setup. | |||
2) Archived channels | |||
3) Possibly other EPICS data sources like Alarm channels? | |||
Hoping to use something existing. Get OpenLDAP [http://www.openldap.org] and check the following: | Hoping to use something existing. Get OpenLDAP [http://www.openldap.org] and check the following: | ||
* Can it be used to store record names, server addresses, maybe more ('primary' server, fields, ...)? Try a simple setup, use the command-line ldapsearch to retrieve data. | * Can it be used to store record names, server addresses, maybe more ('primary' server, fields, ...)? Try a simple setup, use the command-line ldapsearch to retrieve data. | ||
Revision as of 16:41, 5 May 2005
Task
Investigate a network client API for data and name resolution.
Name Server
What would a name server look like that supports
1) Life channels (ChannelAccess), including channels provided by backup systems in a redundant setup.
2) Archived channels
3) Possibly other EPICS data sources like Alarm channels?
Hoping to use something existing. Get OpenLDAP [1] and check the following:
- Can it be used to store record names, server addresses, maybe more ('primary' server, fields, ...)? Try a simple setup, use the command-line ldapsearch to retrieve data.
- Does it allow for redundant servers, automatically syncing?
- How to best interface it (API)?
Data
Is the low-level V4 CA client API all that's needed? Or is a wrapper needed that e.g. holds the data in a container?
- Waiting for 'caget' example code.
