Randall Gellens wrote:
> > (3) When the session is finished by the user, the QPopper will update te
> > contents of the mail file. Here we have to main scenarios:
> > A) The user delete all the messages in the mail file. QPopper leaves the
> > mail file with 0 bytes (this is a very quick operation).
> > B) The user leaves messages in the server. The mail file needs to be
> > updated. The QPopper has to read all the contents of the mail file again
> > and write it to a temporary file including the needed modifications.
> > Next it has to read all the temporary file and copy it over the original
> > mail file. If the mail file size is big this read-write-read-write
> > process takes lot of CPU time and I/O resources.
>
> You can improve the latter situation by using server mode, which
> helps greatly if (a) all mail is deleted, or (b) all mail is left on
> the server and no new mail was present in this session.
In the (b) case, the mail spool will need to be upated if there is new
mail (QPopper adds the header X-UIDL).
Greetings.
---
Carles Xavier Munyoz Bald� / [EMAIL PROTECTED]
Wanadoo Espa�a
Dpto. Sistemas / System Department
Tel: +34 96 5040000 Ext. 40046 - Fax: +34 96 5040047
http://www.wanadoo.es/
---
