Difference between revisions of "V4 Name Server"
KayKasemir (talk | contribs) |
KayKasemir (talk | contribs) (JNDI) |
||
| Line 12: | Line 12: | ||
* Does it allow for redundant servers, automatically syncing? | * Does it allow for redundant servers, automatically syncing? | ||
* How to best interface it (API)? | * How to best interface it (API)? | ||
== API == | |||
Gasper suggested to look at the Java JNDI API for inspiration. | |||
Quote from his emai: | |||
Java has a language-neutral interface to Naming and Directory service, in packages javax.naming.*. Again, can be consulted for an inspiration or actually used in client sw, because it is designed to be an IF through which Java clients access CORBA Naming, LDAP, file system, ... It is simple, small and modular (if you need only naming, you can use it without a directory services, such as search and attributes, etc). | |||
Revision as of 14:25, 10 May 2005
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)?
API
Gasper suggested to look at the Java JNDI API for inspiration. Quote from his emai:
Java has a language-neutral interface to Naming and Directory service, in packages javax.naming.*. Again, can be consulted for an inspiration or actually used in client sw, because it is designed to be an IF through which Java clients access CORBA Naming, LDAP, file system, ... It is simple, small and modular (if you need only naming, you can use it without a directory services, such as search and attributes, etc).
