RFC7888 LITERAL #43

Closed
opened 2023-12-29 17:21:27 +00:00 by quentin · 0 comments
Owner

The Internet Message Access Protocol (RFC 3501) contains the
"literal" syntactic construct for communicating strings. When
sending a literal from client to server, IMAP requires the client to
wait for the server to send a command continuation request between
sending the octet count and the string data. This document specifies
an alternate form of literal that does not require this network round
trip.

imap_codec support: YES
https://docs.rs/imap-types/latest/imap_types/#supported-imap-extensions

https://datatracker.ietf.org/doc/html/rfc7888
https://datatracker.ietf.org/doc/html/rfc2088

> The Internet Message Access Protocol (RFC 3501) contains the "literal" syntactic construct for communicating strings. When sending a literal from client to server, IMAP requires the client to wait for the server to send a command continuation request between sending the octet count and the string data. This document specifies an alternate form of literal that does not require this network round trip. imap_codec support: YES https://docs.rs/imap-types/latest/imap_types/#supported-imap-extensions https://datatracker.ietf.org/doc/html/rfc7888 https://datatracker.ietf.org/doc/html/rfc2088
quentin added this to the 0.2.0 milestone 2023-12-29 17:21:27 +00:00
quentin added the
cat
feature
label 2023-12-29 17:21:27 +00:00
quentin added this to the IMAP4REV2 project 2023-12-29 17:21:27 +00:00
Sign in to join this conversation.
No description provided.