SYNCHRONIZATION OPERATIONS FOR DISCONNECTED IMAP4 CLIENTS
draft-ietf-imap-disc-00
| Document | Type |
Expired Internet-Draft
(imap WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Rob Austein | ||
| Last updated | 1994-11-09 (Latest revision 1994-06-21) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | ftp.cac.washington.edu%3A~/imap/imap_archive | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This note attempts to address some of the issues involved in building a disconnected IMAP4 client. In particular, it deals with the issues of what might be called the 'driver' portion of the synchronization tool: the portion of the code responsible for issuing the correct set of IMAP4 commands to synchronize the disconnected client in the way that is most likely to make the human who uses the disconnected client happy.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)