Friday, May 14, 2004

Application Configuration

Has anyone thought well and hard about application configuration?

First on, what is ACAP?

ACAP is an IETF standard. RFC 2244

How does it rate against other protocols?

Summary of the comparisons against other protocols

M. Wall [Page 3]

Internet DRAFT ACAP VS. OTHER PROTOCOLS September 11, 1996



    ACAP LDAP,et al DHCP SNMP HTTP DNS NFS,AFS et al Data bases
FEATURE Disconnected use Yes No No No No No*1 No*2 No*3
Client-writable Yes Yes No Yes*4 No No Yes Yes
Potentially Large Yes Yes No ? No No Yes Yes
Access Control List Yes Yes No Yes No No Yes No
User Storage Yes No No No ? No Yes No
Client-Definable Yes No No No ? Yes*5 Yes Yes
Per-userSecurity Yes Yes ? No ? No Yes Yes
Server-searching Yes Yes No ? No No No*6 Yes
client/server Yes Yes Yes Yes Yes Yes No No
non-proprietary Yes Yes Yes Yes Yes Yes No No

Yes = has this characteristic
No = does not have this characteristic
? = not fully implemented or unclear if this could support this feature
* = qualified yes or no, see footnote

This chart addresses capabilities, not necessarily typical use

(such as SNMP's client-writing capability).


1. Only via the cache, which is static and non-authoritative.

2. Typically limited scalability; limited real use.

3. Transaction-locking models make this highly implementation-dependent.

4. The MIB is typically authoritative, however.

5. Usually used for limited local override, i.e. trusting a hosts file.

6. Some filesystems can search, but usually without much structure.

Most don't except through OS extensions, anyway.

Any White Papers?

Any implementations?


Infotrope ACAP Server


Any other stuff that might be interesting?

GConf – Gnome Configuration

Configuration maintenance for distributed applications management

Patterns for
Concurrent, Parallel, and Distributed Systems



EDG Fabric Management

Epio Business

SmartFrog - Smart Framework
for Object Groups

The MANDAS Project


Some More Links


No comments:

Post a Comment