james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "robert burrell donkin" <robertburrelldon...@gmail.com>
Subject Re: Mime4j and buffering
Date Tue, 10 Jul 2007 19:41:42 GMT
On 5/31/07, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> Hi,
> On 5/31/07, Norman Maurer <norman@apache.org> wrote:
> > Can you please elaborate what a lookahead buffer is ?
> I'm planning to use a buffer (even a mapped one if using nio) to load
> larger chunks of the message being parsed. The parser can then "look
> ahead" in the buffer to find the next multipart boundary without
> having to check each byte individually.

any progress?

the biggest issue ATM with JAMES IMAP is that MIMEMessage really isn't
a suitable intermediary representation. it's nether efficient nor
accurate. i've taken a look at the current mime4j API. i like it but
try as i might, a streaming push API just isn't efficient for IMAP.

- robert

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message