> here is a proposal on how to implement Sieve.
> 1) Implement a Java implementation of Sieve that...
> a) Accepts a script read from a java.io.InputStream and a
> javax.mail.internet.MailMessage as input.
I assume that you meant MineMessage. I am leaning against using MimeMessage
for specific reasons. Please review in detail the RFC 3028 operations.
*If* we can implement them against a Stream, I think that we would be better
off because the MimeMessage interface really expects that at least once you
start processing the message, it is memory resident. I'm concerned about
performance and scalability with our Sieve implementation. Implementing a
MimeMessage subclass that doesn't expect to be memory resident appears to
involve largely rewriting the package.
Thoughts?
With respect to Serge's comment about a separate CVS repository, we could
have james-sieve, but please be aware that sometime next year, we will be
switching from CVS to Subversion, and probably all ASF code will reside in a
single SVN repository.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
