Hi, sorry it took me a bit longer to answer, I think costum flags is the prefered way to go..
Any thoughts ? Bye, Norman PS: Thx for joining this thread 2009/6/30 Robert Burrell Donkin <[email protected]>: > On Tue, Jun 30, 2009 at 10:22 AM, Christian > Grobmeier<[email protected]> wrote: >> Hi there, >> >> I know, I am not Robert :-) >> However, maybe Google Gears is a solution? It provides an SQLite >> database on browser side. Actually GMail offers support for it. To >> make Hupa work with general IMAP stuff this could be an idea. I am >> thinking on linking message ids to categories and storing that data in >> some magic place within the IMAP folder. > > the folder analogy often used by IMAP clients IMHO often leads to > confusion so i'll - quickly - go through the way i understand them. > > each IMAP mailbox is an ordered list of emails each with a UID. the > concept of email is essentially any enveloped, mime-typed document. so > (in theory) IMAP could reasonably be bridged to other message types. > in practice shoving arbitrary magic documents in is likely to confuse > clients and users. > > i suspect that either using one of the existing IMAP mechanisms (for > example, custom flags) or using a side channel (for example, > JSON-over-HTTP taking advantage of the natural URL structure given by > IMAP) > > message IDs are interesting :-/ > > of particular interest: > > 1. message IDs are not hashes, so it's perfectly possible for emails > to have the same message ID but have some differences > > 2. IMAP message content is immutable. so when messages are copied, the > headers are preserved, including message. whether the message is > actually copied depends on the IMAP server implementation (for > performance reasons, i prefer not to). AIUI in theory, IMAP > implementations should really act as if they ignore message ID but at > least some clients (for example, thunderbird) are more usable if it is > not ignored. > > however, using the message ID would have some nice properties. emails > with the same message ID should be closely related. so, for tagging it > might be useful. > > - robert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
