----- Original Message ----- From: "Peter M. Goldstein"
> The primary goal of this plan is to get a stable, scalable, and > functional James 2.1 out in October. Would you consider : - Mail Streaming support. Mail should never be held in memory. - Clustering support. i.e. Background processors, Mailets etc could run in different processes and machines. - At most parse a mail message once. To me these are absolutely essential to address scalability. Maybe there should be James and James 2 branch. The latter would only focus on scalability and performance, and former on stability with current architecture. I really don't think the current architecture can address these somewhat essential scalability issues well. For instance the entire MailImpl, Mailet structure could work against it. thoughts... Harmeet -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
