Jump to content

Application Configuration Access Protocol

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by EagleOne (talk | contribs) at 02:10, 17 December 2005 (fixed several links). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The Application Configuration Access Protocol (ACAP) is a protocol which enhances IMAP by allowing the user to set up address books, user options, and other data for universal access.

["Your E-Mail Is Obsolete", Byte, Feb 1997 ].

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. It's rumoured to be the most complex Internet Engineering Task Force designed protocol ever, which has caused serious problems for server implementors. It's also markedly similar to Lightweight Directory Access Protocol on some levels, which has caused confusion.

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.

See also

This article is based on material taken from the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Application_Configuration_Access_Protocol&oldid=31685117"