Stable identifiers with UIDL
03UIDL supports recognizing messages across sessions without relying on temporary message numbers.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 7 ↗
RFC 1939 · § 7EXAMPLE
3 / 3
03
Compare after reconnect
Use identifiers to avoid treating old messages as newly arrived.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
UIDL is an optional command in this publication.
- UIDL is an optional command in this publication.
- An identifier persists across sessions for that message under the defined rules.
- Clients need the capability and server semantics rather than assuming message number 1 is always the same message.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy