You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Jochen Wiedmann (JIRA)" <se...@james.apache.org> on 2007/07/11 22:49:04 UTC
[jira] Updated: (MIME4J-19) Pull Parser
[ https://issues.apache.org/jira/browse/MIME4J-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Wiedmann updated MIME4J-19:
----------------------------------
Attachment: mime4j-iterator.patch
Suggested patch.
> Pull Parser
> -----------
>
> Key: MIME4J-19
> URL: https://issues.apache.org/jira/browse/MIME4J-19
> Project: Mime4j
> Issue Type: New Feature
> Affects Versions: 0.3
> Reporter: Jochen Wiedmann
> Fix For: 0.4
>
> Attachments: mime4j-iterator.patch
>
>
> The attached patch introduces a new class called MimeTokenStream, which is a "Pull Parser" for MIME documents. The class is basically a rewrite of the MimeStreamParser. The patch does also provide a rewrite of the MimeStreamParser itself, based on the MimeTokenStream.
> Pull parsers are technically a little bit more difficult. However, from the users perspective, they are much more preferrable, because writing an application on top of a pull parser is much easier than based on an event handler.
> I would like to rewrite the commons-fileupload component based on mime4j. However, as commons-fileupload provides a pull parser API, we depend on the presence of a similar API in mime4j. Not providing a pull parser API would mean, that we'd need to duplicate mime4j code into commons-fileupload, which is certainly not desirable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Updated: (MIME4J-19) Pull Parser
Posted by Norman Maurer <no...@apache.org>.
Maybe I will be able today to have a look at it.
bye
Norman
On Thu, 12 Jul 2007 20:39:52 +0100, "robert burrell donkin" <ro...@gmail.com> wrote:
> i think that having a pull parser at MIME4J would be cool :-)
>
> anyone more knowledgeable fancy taking a look at this patch?
>
> - robert
>
> On 7/11/07, Jochen Wiedmann (JIRA) <se...@james.apache.org> wrote:
>>
>> [
> https://issues.apache.org/jira/browse/MIME4J-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>>
>> Jochen Wiedmann updated MIME4J-19:
>> ----------------------------------
>>
>> Attachment: mime4j-iterator.patch
>>
>> Suggested patch.
>>
>>
>> > Pull Parser
>> > -----------
>> >
>> > Key: MIME4J-19
>> > URL: https://issues.apache.org/jira/browse/MIME4J-19
>> > Project: Mime4j
>> > Issue Type: New Feature
>> > Affects Versions: 0.3
>> > Reporter: Jochen Wiedmann
>> > Fix For: 0.4
>> >
>> > Attachments: mime4j-iterator.patch
>> >
>> >
>> > The attached patch introduces a new class called MimeTokenStream,
> which is a "Pull Parser" for MIME documents. The class is basically a
> rewrite of the MimeStreamParser. The patch does also provide a rewrite of
> the MimeStreamParser itself, based on the MimeTokenStream.
>> > Pull parsers are technically a little bit more difficult. However,
> from the users perspective, they are much more preferrable, because
> writing an application on top of a pull parser is much easier than based
> on an event handler.
>> > I would like to rewrite the commons-fileupload component based on
> mime4j. However, as commons-fileupload provides a pull parser API, we
> depend on the presence of a similar API in mime4j. Not providing a pull
> parser API would mean, that we'd need to duplicate mime4j code into
> commons-fileupload, which is certainly not desirable.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
> !DSPAM:1,469683ac240378290022044!
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Updated: (MIME4J-19) Pull Parser
Posted by robert burrell donkin <ro...@gmail.com>.
i think that having a pull parser at MIME4J would be cool :-)
anyone more knowledgeable fancy taking a look at this patch?
- robert
On 7/11/07, Jochen Wiedmann (JIRA) <se...@james.apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/MIME4J-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jochen Wiedmann updated MIME4J-19:
> ----------------------------------
>
> Attachment: mime4j-iterator.patch
>
> Suggested patch.
>
>
> > Pull Parser
> > -----------
> >
> > Key: MIME4J-19
> > URL: https://issues.apache.org/jira/browse/MIME4J-19
> > Project: Mime4j
> > Issue Type: New Feature
> > Affects Versions: 0.3
> > Reporter: Jochen Wiedmann
> > Fix For: 0.4
> >
> > Attachments: mime4j-iterator.patch
> >
> >
> > The attached patch introduces a new class called MimeTokenStream, which is a "Pull Parser" for MIME documents. The class is basically a rewrite of the MimeStreamParser. The patch does also provide a rewrite of the MimeStreamParser itself, based on the MimeTokenStream.
> > Pull parsers are technically a little bit more difficult. However, from the users perspective, they are much more preferrable, because writing an application on top of a pull parser is much easier than based on an event handler.
> > I would like to rewrite the commons-fileupload component based on mime4j. However, as commons-fileupload provides a pull parser API, we depend on the presence of a similar API in mime4j. Not providing a pull parser API would mean, that we'd need to duplicate mime4j code into commons-fileupload, which is certainly not desirable.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org