Application Configuration Access Protocol: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
| ⚫ | |||
The '''Application Configuration Access Protocol''' (ACAP) is a protocol for storing and synchronizing general configuration and preference data. It was originally developed so that [[Internet Message Access Protocol|IMAP]] clients can easily access [[address book]]s, user options, and other data on a central server and be kept in synch across all clients. |
The '''Application Configuration Access Protocol''' (ACAP) is a protocol for storing and synchronizing general configuration and preference data. It was originally developed so that [[Internet Message Access Protocol|IMAP]] clients can easily access [[address book]]s, 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. |
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. |
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. |
||
| Line 12: | Line 9: | ||
The [[IETF]] ACAP Working Group ceased activity in April 2004,[http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg00091.html] having released two [[Request for Comments|RFCs]], RFC 2244 ("ACAP — Application Configuration Access Protocol") and RFC 2245 ("Anonymous SASL Mechanism"). |
The [[IETF]] ACAP Working Group ceased activity in April 2004,[http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg00091.html] having released two [[Request for Comments|RFCs]], RFC 2244 ("ACAP — Application Configuration Access Protocol") and RFC 2245 ("Anonymous SASL Mechanism"). |
||
==References== |
|||
| ⚫ | |||
==See also== |
==See also== |
||
| Line 21: | Line 21: | ||
*[[IMSP]] |
*[[IMSP]] |
||
*[[SyncML]] |
*[[SyncML]] |
||
| ⚫ | |||
==External links== |
==External links== |
||
*[http://cyrusimap.web.cmu.edu/downloads.html#acap CMU smlacapd] |
*[http://cyrusimap.web.cmu.edu/downloads.html#acap CMU smlacapd] |
||
| ⚫ | |||
[[Category:Internet mail protocols]] |
[[Category:Internet mail protocols]] |
||
Revision as of 09:41, 21 December 2009
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,[1] having released two RFCs, RFC 2244 ("ACAP — Application Configuration Access Protocol") and RFC 2245 ("Anonymous SASL Mechanism").
References
["Your E-Mail Is Obsolete", Byte, Feb 1997 ].
See also
External links
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.