Mitch (WebCob) wrote:
Yeah - problem would be support thereof... If I just did it say once every
10 minutes, I'd be guaranteed to have 1 in 1000 freaking out because of a
horendous typo they just found out about, which they corrected and isn't
reflected in their tests (assuming they test ;-)
You'll get that no matter what you do. Even if it were dynamic, they'd
get no response at all on their second try (mailbot won't send mail
again for a few days). They freak. It's what users do. :)
I'd have to dump them all pretty often, or have to change the database to
detect change time on the memo and select / dump based on that, which I
guess I could do as well, just seemed like an icky work around.
You can do that... Datestamp each entry in the database. Every 5
minutes, update all of the files whose db entry has changed in the last
10. Either that or (more reliable), create a second table with just one
column containing a datestamp. Save it's value, update the row with the
current time before you begin, and update all of the files whose db
entry changed after the old datestamp.
Figured I'd see if someone else was struggling with the same issue ;-)
I have.
I wonder which would be worse - a query per mail for the small percentage of
users on vacation, or a query per minute for all the users, rewriting
changed vacation messages as I go ;-)
Your own time is probably more valuable than the computer resources
required. Updating static files will require a lot less maintenance in
the future and, properly implemented, it's more efficient in computing
resources, too.
4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] mailbot for virtu...
