Martin Kauss schrieb:
On Jul 19, 2005 09:57 AM, Chris Burdess <dog(a)bluezoo.org>
>Tom Tromey wrote:
>>Chris> If you just want ACL support in the GNU IMAP provider, we can
>>Chris> it in for the next release.
>>Martin> We can help to make such an implementation happen, but our
>>Martin> focus is the solution and the features. Thats why we have not
>>Martin> ask for methods. Now, if there is a strong demand and the GNU
>>Martin> Classpath developers are scheduling the complete
>>Martin> implementation of the required classes and methods for one of
>>Martin> the next GNU Classpath javamail API releases, we should have
>>Martin> some conversation how this can be implemented in a very easy
>>Martin> way (like some kind of configure option) to support it (of
>>Martin> course we must keep an eye on the effort ;-).
>>Martin> And to avoid any rumor, this strategy is part of our general
>>Martin> developing concepts. We do not reinvent wheels we are using
>>Martin> existing infrastructure wherever it fits our needs.
>>Let me make a somewhat more radical suggestion: if inetlib implements
>>the needed ACL support, how about switching to use it exclusively?
First of all, you shouldn't only write to one person. The mailing list should be
used to allow everyone to participate this discussion.
>It does; the relevant IMAPConnection methods are setacl,
>getacl, listrights, myrights.
>It wouldn't be too much trouble to implement higher-level wrappers in
>IMAPFolder if working with them is conceptually easier, though. Also,
>as I mentioned before, JavaMail and JAF provide a whole MIME
>implementation that may be convenient.
I think there are two possible solutions for this problem:
1. Start a Java Specification Request (JSR) that integrates ACLs into the non
provider specific Java Mail API.
2. The author of Webmail has to add an abstract layer that implementations uses
Sun provider specific or GNU classpath specific API for ACLs. This can be done
through the GOF Design Pattern "Bridge".
i will talk with Stefan about this over the next week
(he is not available this week) - we will come back
This are just my two cents that lead to a functional implementation that can
base on commercial and free implementations. It must simply work for the normal