Thanks Noel, I'll sniff around. I took a quick look at the mail repository code. The current MailRepositories don't seem designed to handle folder structures, just a monolithic mailbox... is that right? Or is the idea to nest MailRepositories within each other?
Also, anyone have any idea about the scaling characteristics of the MailRepositories and/or James in general? Is there a practical CPU/RAM limit to how big a single mailbox can be? What's the most number of total/concurrent users people have had? What kind of usage scenarios was James designed for--is it the kind of system that could, say, replace sendmail and qpopper for an ISP? Thanks... > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 19, 2003 1:35 AM > To: James Developers List > Subject: RE: imap > > > Joe, > > You might take a look at the code in proposals/imap2. I > haven't looked at the code. Basically, the various handlers > all work by having a > handleSocket() method, which is coming from Avalon. I expect > that we'll have to change that eventually to complete the > inversion in order to handle both java.io and java.nio. > > --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
