G'day, On Wed, 13 Mar 2002 09:09, Danny Angus wrote: > Hi, > Storing them in a db gives you potentially a number of advantages some of > which are listed below.. > 1/ it allows any application capable of connecting and using SQL to access > the information, such as a webmail application, account management, or > inserting messages directly into the spooler (instead of via SMTP)
Just to be contrary, I see this as a disadvantage ;). I think that *any* code that wants to get at the database (Users, Messages etc) should go via an API (existing or new), so that the storage is independent of the code. I think we should discourage people from accessing the database directly in their applications, because it becomes another compatibility layer we have to support. (ie If we want to change the database structure (to move to IMAP storage, say), we should just be able to say, "run this SQL script and you're away". But if people are accessing the database directly, we'll be breaking their code as well.) This is not to say that it's not immensely useful to browse the tables manually, but I don't feel good about applications going "under the radar" so to speak. Of course, people will still do it, but I don't reckon it should be the sanctioned James way. just a thought, ciao Daz -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
