presuming you were storing the message in a file on disk, you could
adopt some sort of meta structure, where the message was a part, and
envelopes became other parts (and annotations if desired). This could
be as simple as putting a length at the start of the message to where
the envelopes start. Any sort of structure I'd length-prefix, so you
can skip data instead of having to scan it.
the server would take care of it all, and clients would just fetch the
bits they wanted. Being in a single file would solve issues relating to
synchronisation / keeping it all together.
On 21/02/2012 3:46 a.m., Bron Gondwana wrote:
On Mon, Feb 20, 2012, at 02:43 PM, Dave Cridland wrote:
On Mon Feb 20 14:35:35 2012, Bron Gondwana wrote:
It probably means storing annotations - or at least providing a way
to access this envelope data that smells remarkably like
annotations.
No.
Store it as a properly modelled transport envelope - no need to turn
it into magic soup - that's never worked.
Fine with me. It's just yet another axis of data tied to a message, and
it needs its very own "keywords" or "annotations" as well, presumably, if
you want to note when it was accepted, or MDNed.
Bron.
--
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com
WinGate 7 is released! - http://www.wingate.com/getlatest/
_______________________________________________
imap5 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imap5
