Extra Header field

[Stuart K. Bingë]

On Monday, 12 July 2004 19:18, Martin Konold wrote:
> Ok, this is what I expected. But I am now really wondering why the Horde
> client cant keep a simple mapping <uid>,<imap-uid> in the session. After
> all the Horde client must parse every message anyway before it has the
> complete calendaring information.

This will not be practical, as like I said, the IMAP UID is not constant 
across object modifications. This means I will have to deal with the 
possibility of holding an incorrect UID mapping.

For example, it may be the case that between when I initially load a mailbox 
and form this mapping, to when I need to load up a specific object, something 
or someone has modified the mailbox and consequently messed up my UID 
mapping, without me even knowing about it.

> In case the caldendar changes while the Horde client has a local
> representation it has to parse _every_ new IMAP message anyway.

That's true. But if all I want to do is load an object, given its UID, and if 
the UID is stored in a header, I can then perform a SEARCH on the mailbox to 
load the message of interest without having to touch the rest of the 
messages, which are of absolutely no relevance to the operation.

It's only the case that I *need* to reload the entire message box when I'm 
generating a complete listing page. Unless, that is, that the UID is not 
stored in a header, in which case I will need to reload the entire messagebox 
when all I really want to do is load a single message.

-- 
Stuart Bingë
Code Fusion cc.

Office: +27 11 673 0411
Mobile: +27 83 298 9727
Email: s.binge at codefusion.co.za

Tailored email solutions; Kolab specialists.
http://www.codefusion.co.za/