Hi guys, I'm new to the list, so here's my first question.
Why does james use files for persistence at all. It seems to me that you could always use a DB, and if the user didn't
want to set up a DB you could just run hsql in process and use it as your persistence engine. That would eliminate
the need for you to write all that file code. It just strikes me as odd that everyone always wants to use their own file
IO system for persistence when it seems that is exactly what hsql is there for.
First and foremost, it's because the IO code was written 4 years ago. Second, it was written and supposed to be maintained by the Avalon project, so we were supposed to be getting something for free.
We've talked about using hsql or something like that, but I think the issue is frankly performance. I use hsql with great results with small datasets, but James can easily have 1+ gigs in messages and individual messages (a db record) can be 10 megs.
Even real database servers do not handle the huge messages gracefully (we often recommend using file in certain scenarios for performance reasons). I'm not knowledgeable enough to say that hsql isn't viable, but I am pessimistic.
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
