> So the server cannot send an expunge response until it can be sure > the client has not queued up loads of fetches for sequence > numbers that might have been invalidated. > > Such a sync point can be forced by the client by sending > noops more often > or entering an explicit idle state with the idle extension. >
Agreed that given a rapid queue of FETCHes getting an expunge would cause an issue. However, the problem occurs for clients that do FETCH 1 Wait 29.5 minutes FETCH 2 Wait 29.5 minutes FETCH 3 The server writer is being forced to make unreasonable and IMHO stupid decisions because the client MAY do that. Where is the section that says "Clients should issue NOOP or CHECK at intervals not exceeding x seconds" Or "Clients should issue NOOP or CHECK before or after a rapid sequence of FETCHes...." Or "Clients that don't allow the server to resync by sending a NOOP can expect fetches to fail and should then issue a NOOP". The responses always seem to be "The server should allow the client to do any damn thing they please, no matter how stupid, as long as its in the protocol". Regards Richard Bang Floosietek Ltd [EMAIL PROTECTED] http://www.floosietek.com
