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 Sun, 15 Jul 2007 18:21:17 GMT
On 7/11/07, robert burrell donkin <robertburrelldonkin@gmail.com> wrote:
> On 7/11/07, Jochen Wiedmann <jochen.wiedmann@gmail.com> wrote:
> > robert burrell donkin-2 wrote:
> > >
> > > On 5/31/07, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> > >
> > >> 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?
> > >
> >
> > It took me about 4 hours to create the patch for MIME4J-19. (Pull parser
> > API)
>
> cool :-)
>
> (i've heard that cxf also has an email pull parser - be interesting to
> compare designs)
>
> > Given my experiences with commons-fileupload, I believe it would take
> > another 6 hours or so to rewrite MIME4J-19 a second time in order to use a
> > single, buffered InputStream, which would even be able to provide
> > information like line and column number and byte offset.
>
> sounds interesting :-)

i've had a play around this afternoon and think this could be the best way to go

> i've been thinking about nio and parsers for bytebuffers recently.
> (the current JAMES IMAP implementation stores the bodies in byte
> arrays.)

it should be reasonably easy to add basic support for parsing data in
a byte buffer but it'll need to wait until the pull parser is
committed

- robert

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


Mime
View raw message