On 7/11/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
robert burrell donkin-2 wrote:
>
> On 5/31/07, Jukka Zitting <[EMAIL PROTECTED]> 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 been thinking about nio and parsers for bytebuffers recently.
(the current JAMES IMAP implementation stores the bodies in byte
arrays.)
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
