[haiku-development] Re: [GSoC proposal] IMAP FS - A few queries

  • From: Donn Cave <donn@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Thu, 14 Apr 2011 16:19:25 -0700 (PDT)

Quoth Anshul Singhle <xashck@xxxxxxxxx>,
>> There could be more useful ways to present it, but that opens up a whole
>> can of
>> worms.
>>
>> Just to be clear here: you are talking about the Filesystem storing the
> encoded data from FETCH. I would prefer to parse the data first and store
> only what is relevant. e.g. in a multipart message, get the MIME information
> from bodystructure and store fields like the octet size or rather the octet
> offsets as file attributes. For a large message this might prove to be
> tricky though but AFAIK i haven't heard of too many messages with say >10
> parts.

Sorry, I didn't follow that.  I think you have two reasonable choices:
1. present the MIME structure intact in one file, encoded and with the
   headers that describe the encoding, or
2. you decode the parts and present them as separate files.  That's where
   I saw a can of worms, the problem of presenting some messages as files
   and others as collections of files.  There's no question it's good for
   the application, layer, I just don't see how it would work.

> On a related note, the handling of threads is also another question. Would
> the mail thread be stored as an attribute or is there a better way of
> representing threads. If the thread a message belongs to is stored as an
> attribute, it would be possible to get threads via queries so i guess that
> should be enough.

I personally would leave threading to the application layer.  I think
there may be more than one possible algorithm, for one thing.

        Donn

Other related posts: