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/23 22:17:31 UTC
[jira] Assigned: (MIME4J-19) Pull Parser
[ https://issues.apache.org/jira/browse/MIME4J-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Wiedmann reassigned MIME4J-19:
-------------------------------------
Assignee: Robert Burrell Donkin
Robert, I gave you edit rights for mime4j. A question to the group: Wouldn't it be better, if the role "james-developers" had edit permissions?
> 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
> Assignee: Robert Burrell Donkin
> Fix For: 0.4
>
> Attachments: cursored-pull.patch, 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 permissions UPDATED! (Was: [jira] Assigned: (MIME4J-19) Pull Parser)
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On 7/24/07, norman <no...@apache.org> wrote:
> Thx to get rid of this :-)
+1
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: JIRA permissions UPDATED! (Was: [jira] Assigned: (MIME4J-19)
Pull Parser)
Posted by norman <no...@apache.org>.
Thx to get rid of this :-)
bye
Norman
Am Dienstag, den 24.07.2007, 00:40 +0200 schrieb Stefano Bagnara:
> Jochen Wiedmann (JIRA) ha scritto:
> > [ https://issues.apache.org/jira/browse/MIME4J-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> >
> > Jochen Wiedmann reassigned MIME4J-19:
> > -------------------------------------
> >
> > Assignee: Robert Burrell Donkin
> >
> > Robert, I gave you edit rights for mime4j. A question to the group: Wouldn't it be better, if the role "james-developers" had edit permissions?
>
> I had a look at this, and it was a real mess ;-)
>
> So I rewrote the whole schema permission for JAMES projects (JAMES,
> POSTAGE, JSIEVE, JSPF, MIME4J, MAILET)
>
> - created a new group names james-pmc including the james-pmc members.
>
> - updated the james-developers to include every member previously listed
> in a committer or contributor role for one of the above projects.
>
> - removed user-specific permissions for every project
>
> - added "JIRA administrator" and "JIRA pmc" roles to the james-pmc group.
>
> - added "JIRA committer" and "JIRA contributor" roles to the
> james-developers group.
>
> - left the permission scheme to the "Standard" ASF permission scheme.
>
>
> I hope this is simple enough to be better mantained in future.
>
> In summary the biggest change is that I gave much more power to our PMCs
> (administration rights on the JAMES projects seems the right thing to
> me). Previously only jira-administrators could have done substantial
> changes to JAMES projects.
>
> Here is the current list of james-developers members:
> ----
> bago
> brainlounge
> charles_#_benett1.demon.co.uk
> danny_#_apache.org
> hilmer_#_apache.org
> jefft
> joachimdraeger
> jw_#_inovem.com
> niklas_#_trillian.se
> noel
> norman
> robertburrelldonkin
> sbrewin_#_apache.org
> serge
> vincenzo
> -----
>
> Here is the current list of james-pmc members:
> ----
> bago
> brainlounge
> danny_#_apache.org
> hilmer_#_apache.org
> noel
> norman
> robertburrelldonkin
> sbrewin_#_apache.org
> serge
> vincenzo
> -----
>
> If something is wrong feel free to insult me, you'll be
> ignor^H^H^H^H^H^H^H^H I'll fix it ;-)
>
> Stefano
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
> !DSPAM:1,46a52ecc240371200712141!
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
JIRA permissions UPDATED! (Was: [jira] Assigned: (MIME4J-19) Pull
Parser)
Posted by Stefano Bagnara <ap...@bago.org>.
Jochen Wiedmann (JIRA) ha scritto:
> [ https://issues.apache.org/jira/browse/MIME4J-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jochen Wiedmann reassigned MIME4J-19:
> -------------------------------------
>
> Assignee: Robert Burrell Donkin
>
> Robert, I gave you edit rights for mime4j. A question to the group: Wouldn't it be better, if the role "james-developers" had edit permissions?
I had a look at this, and it was a real mess ;-)
So I rewrote the whole schema permission for JAMES projects (JAMES,
POSTAGE, JSIEVE, JSPF, MIME4J, MAILET)
- created a new group names james-pmc including the james-pmc members.
- updated the james-developers to include every member previously listed
in a committer or contributor role for one of the above projects.
- removed user-specific permissions for every project
- added "JIRA administrator" and "JIRA pmc" roles to the james-pmc group.
- added "JIRA committer" and "JIRA contributor" roles to the
james-developers group.
- left the permission scheme to the "Standard" ASF permission scheme.
I hope this is simple enough to be better mantained in future.
In summary the biggest change is that I gave much more power to our PMCs
(administration rights on the JAMES projects seems the right thing to
me). Previously only jira-administrators could have done substantial
changes to JAMES projects.
Here is the current list of james-developers members:
----
bago
brainlounge
charles_#_benett1.demon.co.uk
danny_#_apache.org
hilmer_#_apache.org
jefft
joachimdraeger
jw_#_inovem.com
niklas_#_trillian.se
noel
norman
robertburrelldonkin
sbrewin_#_apache.org
serge
vincenzo
-----
Here is the current list of james-pmc members:
----
bago
brainlounge
danny_#_apache.org
hilmer_#_apache.org
noel
norman
robertburrelldonkin
sbrewin_#_apache.org
serge
vincenzo
-----
If something is wrong feel free to insult me, you'll be
ignor^H^H^H^H^H^H^H^H I'll fix it ;-)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org