I agree with Noel here, filesystem storage has better (in theory) performance for short lists of files, but JDBC should offer *much* less tail off of performance as the number of messages grow, owing to the way messages are de-spooled, basically SQL provides better tools for getting appropriate lists of messages than the current filesystem repositories have.
d. > I am finding that using JDBC for a spool is higher performance > than the file > system, but please test it in your environment. Also, if you are going to > do a backup, one benefit of using JDBC (at some expense of resources) is > that you can configure MySQL to do real-time replication. I use that with > our system such that in the event of a failure of the live > server, I have a > real-time backup. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
