Re: bincdrop status / Binc future [was:1.5]

On Fri, Aug 05, 2005 at 10:12:52PM +0200, Andreas Aardal Hanssen wrote:
>   An IMAP server is expected to:

[..do tricks..]

I guess the modern way is to compile bytecode and run it in a VM..


>   a) Quickly parse and search the toplevel headers.
>   b) Parse the entire document and keep a record of its structure, the
>      headers in all parts and what offsets all parts can be found.
>      Also the size and length in lines of each part of each message.
>   c) Determine the size (converted to CRLF) of the document.
>   d) Search toplevel headers, the "text" parts of the message and the
>      entire message.
>   e) Print any part or all parts of the whole document. And keeping in
>      mind that _any_ combination of any request has to be exactly
>      identical to any other combination requests that add up to the
>      same response, and it all has to add up to the reported structure
>      and total size of the document. To put it simple, if the server
>      claims that part 1.2 contains three subparts, but printing part
>      1.2 reveals only two, or four, then clients go bananas.
> 
>   This is what Binc does today, and it does it quite fast and I/O
>   efficiently. But the API could be better ;-) hehe.

How? I haven't looked at the current API but with the above points in
mind, how could it be improved? Or rather, how would you like it to
work?

clamdmail uses ripmime. I haven't looked at it, have you?


//Peter