[Extra] Response when no Command in Progress (was AD Review of draft-ietf-extra-imap4rev2)

[Alexey Melnikov <[e-mail]>]

Hi Murray,

I've changed subject for this issue, so that it doesn't get lost in 
myriad of other replies.

On 04/01/2021 08:18, Murray S. Kucherawy wrote:

> Section 5.3
>
>
> Maybe my understanding is wrong, but if you do a non-blocking write 
> while you don’t have enough buffer space available, won’t some of what 
> you write be lost, resulting in gibberish at the other end?
>
All the API I've seen tell you how much (possibly 0 octets) were 
written, so a properly written application will not send gibberish. 
Because IMAP is line oriented and, in some cases, octet counted (like 
literals), a partial write is never a problem on the receiving side.
>
> Maybe this needs to mention retries of stuff that couldn’t be sent (if 
> any) when a non-blocking write returns?
>
Possibly. Can you suggest some text on this point?
>
> I’m tempted to suggest just removing this.  This is something you deal 
> with at the socket layer, and IMHO isn’t really part of IMAP itself.
>
Personally, I found warning in this section useful. If it is removed, it 
is not going to change my implementation ;-).

But seriously: I think I would like WG's feedback on this one.

Thank you,

Alexey