V4 Name Server
From EPICSWIKI
Revision as of 17:11, 5 May 2005 by KayKasemir (talk | contribs) (→Channel Access Client User Interface)
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)?
Channel Access Client User Interface
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. How easy is it to implement a simple command-line tool to get a single PV?
- Assert that display tools, archiver, EPICS 'office' can do what they need to do with the CAC API.
