Difference between revisions of "V4 Name Server"
From EPICSWIKI
KayKasemir (talk | contribs) (created) |
KayKasemir (talk | contribs) |
||
| Line 3: | Line 3: | ||
=== Name Server === | === Name Server === | ||
Can | Hoping to use something existing. Get OpenLDAP and check the following: | ||
maybe more ('primary' server, fields, ...)? | * Can it be used to store record names, server addresses, maybe more ('primary' server, fields, ...)? | ||
Does it allow for redundant servers, automatically syncing? | Try a simple setup, use the command-line ldapsearch to retrieve data. | ||
How to best interface it (API)? | * Does it allow for redundant servers, automatically syncing? | ||
* How to best interface it (API)? | |||
=== Data === | === Data === | ||
| Line 12: | Line 13: | ||
Or is a wrapper needed that e.g. holds the data in a | Or is a wrapper needed that e.g. holds the data in a | ||
container? | container? | ||
* Waiting for 'caget' example code. | |||
Revision as of 00:01, 5 May 2005
Task
Investigate a network client API for data and name resolution.
Name Server
Hoping to use something existing. Get OpenLDAP 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.
