On Fri, 2003-08-08 at 04:59, Noel J. Bergman wrote: > Jason, > > Is there something you can do to address the scalability? I didn't realize > until I read through it that you keep the entire mbox in core during > operation. That would prevent it from being used to archive mailing lists, > since those files could grow quite large. > Correct, and as you pointed out less than ideal. However, the mbox is only read into memory when someone wants to read it via James (POP3). If you just want it to store messages then they just get appended to the current mbox file (on disk).
I also have a plan B. I could treat the mbox file like an ISAM file and do all the operations on disk. The only thing I'd have to store in memory would be the keys. Then I would have to write dot-locking as the risk of a collision with another mbox updater would be that much greater. This would be slower, but it would work. Opinions? > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Jason Webb --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
