Hi
sorry, saw this after my last email
------ Original Message ------
From: "Arnt Gulbrandsen" <[email protected]>
IMAP is a bit wasteful of bandwidth in many ways. We have a goodish
solution for that, RFC 4978, and it's fairly well deployed. Of course
we might add Microsoft-like special rules to lessen the pain by each
particular instance of bandwidth waste, but since we already have a
goodish solution for all of them, why bother?
we support 4978 and it's great for sure. There are a lot of clients
that don't support it though.
And it has a non-zero additional CPU cost which therefore must affect
scalability.
But sure, if you're already compressed, then those EXPUNGEs will
compress to nearly nothing.
They should add 4978 to the LEMONADE profile. It does a better job for
mobile clients than some of the other ones.
I think that if you really want to not send EXPUNGE, you should
provide some numbers to argue your case. Take the log files from some
server, analyse the moves. How many messages are affected, and how
many bytes would be sent on average for those commands when a) EXPUNGE
is used b) EXPUNBGE+COMPRESS=DEFLATE c) VANISHED+C=D and d) nothing.
I suspect that b and c will be very, very close to d.
I'm sure you're correct.
My main issue is with interop since we have a legacy issue due to the
current I-D being in the wild now.
Can we just test maybe to see if any existing clients will break on a
MOVE that sends EXPUNGEs? If not, then this may be a non-issue.
Adrien
(FWIW, the easiest way to simulate b/c is to massage an IMAP session
so you get a file containing just what the server sends, and then just
'gzip -1' the prefix up until VANISHED/COMPRESS and until just after
that, and look at the size difference. It won't be exact, but fairly
good. Or 'gzip -4' or even -9.)
Arnt
_______________________________________________
imap5 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imap5
_______________________________________________
imap5 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imap5
