Robert Burrell Donkin ha scritto: >> I've not even investigated this option, but before thinking what the >> real problems could be I want to be sure I'm understanding what you propose! > > messages are typically read more often than they are written. unless > the API is able to offer some gaurantees about the output, it is > forced to assume the worse. > > in practice, this implies re-parsing and re-encoding the complete > message each time any information needs to be read. the code which > took this approach is too slow and uses too much memory to be > reasonably usable even on a quick machine. (several minutes to open a > new mailbox on my AMD64 with 1G RAM allocated to JAMES.)
In SMTP and POP3 this is not a real issue. I don't know IMAP too much. Is it a common case that a message content is read over and over again? I thought that most things was cached on the client side and read very few times from the server. Is this a wrong assumption? Stefano > the MailboxAPI layer is in a position to perform optimisations. it may > elect to re-encode or cache 8bit mime parts. it may decide to > re-encode on the way in or on the way out. > > - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
