Application Configuration Access Protocol

The Application Configuration Access Protocol (ACAP) is a protocol for storing and synchronizing general configuration and preference data. It was originally developed so that IMAP clients can easily access address books, user options, and other data on a central server and be kept in synch across all clients.

Two International ACAP Conferences were held, one in Pittsburgh, PA, USA, in 1997, and the other at Qualcomm Incorporated, San Diego, CA, USA, in February, 1998.

ACAP grew to encompass several other areas, including bookmark management for web browsers -- it's effectively a roaming protocol for Internet applications. ACAP is in use by at least four clients and three servers to varying degrees, but it has never gained the mindshare of Lightweight Directory Access Protocol or SyncML. It's a deceptively simple protocol, but the combination of three key features, hierarchical data, fine-grained access control, and "contexts" or saved searches with notification, has caused serious problems for server implementors.

Unlike LDAP, ACAP was designed for frequent writes, disconnected mode access (meaning clients can go offline and then resynchronize later), and so on. It also handles data inheritance, sometimes known as stacking, which provides easy creation of defaults.

The IETF ACAP Working Group ceased activity in April 2004, having released two RFCs, RFC 2244 ("ACAP — Application Configuration Access Protocol") and RFC 2245 ("Anonymous SASL Mechanism").

Famous quotes containing the words application and/or access:

    I think that a young state, like a young virgin, should modestly stay at home, and wait the application of suitors for an alliance with her; and not run about offering her amity to all the world; and hazarding their refusal.... Our virgin is a jolly one; and tho at present not very rich, will in time be a great fortune, and where she has a favorable predisposition, it seems to me well worth cultivating.
    Benjamin Franklin (1706–1790)

    The Hacker Ethic: Access to computers—and anything which might teach you something about the way the world works—should be unlimited and total.
    Always yield to the Hands-On Imperative!
    All information should be free.
    Mistrust authority—promote decentralization.
    Hackers should be judged by their hacking, not bogus criteria such as degrees, age, race, or position.
    You can create art and beauty on a computer.
    Computers can change your life for the better.
    Steven Levy, U.S. writer. Hackers, ch. 2, “The Hacker Ethic,” pp. 27-33, Anchor Press, Doubleday (1984)