http://70.231.62.181/index.php?action=history&feed=atom&title=Application_Configuration_Access_ProtocolApplication Configuration Access Protocol - Revision history2026-04-22T17:27:43ZRevision history for this page on the wikiMediaWiki 1.45.1http://70.231.62.181/index.php?title=Application_Configuration_Access_Protocol&diff=158023&oldid=previmported>Villaida: added section heading2025-05-25T17:06:37Z<p>added section heading</p>
<p><b>New page</b></p><div>{{Distinguish|text= [[Automated Content Access Protocol]] (ACAP)}}<br />
{{more footnotes|date=January 2013}}<br />
[[File:ACAP-small.png|thumb|right|300px|T-shirt of Second International ACAP Conference]]<br />
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.<br />
<br />
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.<br />
<br />
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 achieved the popularity of [[Lightweight Directory Access Protocol]] or [[SyncML]]. It is 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.<br />
<br />
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.<br />
<br />
The [[IETF]] ACAP Working Group ceased activity in April 2004,<ref>{{cite web |url=http://www.ietf.org/mail-archive/web/ietf-announce/current/msg00091.html |title=WG Action: Conclusion of the Application Configuation Access Protocol (Acap) |website=www.ietf.org |access-date=14 January 2022 |archive-url=https://web.archive.org/web/20110726172340/http://www.ietf.org/mail-archive/web/ietf-announce/current/msg00091.html |archive-date=26 July 2011 |url-status=dead}}</ref> having released two [[Request for Comments|RFCs]], {{IETF RFC|2244}} ("ACAP — Application Configuration Access Protocol") and {{IETF RFC|2245}} ("Anonymous SASL Mechanism").<br />
<br />
==See also==<br />
*[[Kolab]]<br />
*[[iCalendar]]<br />
*[[WebDAV]]<br />
*[[CalDAV]]<br />
*[[IMSP]]<br />
<br />
==References==<br />
{{Reflist}}<br />
<br />
== Further reading ==<br />
{{refbegin}}<br />
* "Your E-Mail Is Obsolete", ''[[Byte (magazine)|Byte]]'', February 1997<br />
{{refend}}<br />
<br />
==External links==<br />
*[https://web.archive.org/web/20061223042629/http://cyrusimap.web.cmu.edu/downloads.html#acap CMU smlacapd]<br />
<br />
{{URI scheme}}<br />
<br />
[[Category:Internet mail protocols]]</div>imported>Villaida