On Aug 21, 2006, at 5:15 PM, Mariano Absatz wrote:

Maybe the "lazyness" can be somehow configurable with sensible defaults (sensible beeing whatever you think is sensible modified by whatever the rest of us think is "plain wrong" and can somehow explain why) :-)

Yes! Since I last mentioned this, I've made some changes, basically
I've actually created some sort of locking scheme - it's very
primitive, but if a mailing is going on, a simple, lock file is
created, sort of like semaphore

http://en
wikipedia
org/wiki/Semaphore_(programming)

If that file exists, Dada Mail won't try to pick up a mailing - easy
enough The lock file is only removed when a mailing is through,
which leads to the problem, "What happens if a mailing doesn't
finish?" Well, the lockfile hangs out

Currently, Dada will check on the Last Time a Message Was Sent - if
it's 3 times as long as a batch rests, plus 60 seconds (for luck!),
the stale lock will be removed Maybe this should somehow be
configuratble

Anyways, that should be enough time to be certain There are some
safety checks, even if the mailing is still going on, so if this
system fails, you still shouldn't get a double mailing

So that's one new change,

The other change is that you can basically have the sleep()ing
between batches not actually happen by having the program sleep
(programmatically) Instead, you have the option of the program,
after finishing a batch, just exit cleanly (and the lockfile gets
removed), and wait until the whole auto-pickup system auto-picks
it up If this is the case, you only wait the amount of time as the
regular interval of a batch is

This situation should probably only be used if your server just
basically drops your process every time you try to make the program
sleep You should basically still use the first option

Finally, I've made batch sending mandatory, and simplified the
range of times you can set a batch to, from 1-60 messages every 1-60
seconds Sounds constrictive, but you should be able to get between
3600 and almost a quarter of a million messages sent using these
settings Should fit everyone's needs :)

And I know all this talking I've been doing gets very technical, but
in the program, it's just two new checkboxes to check Pretty cool

Oh! And I've made a cronjob script version of the web-based sending
monitor thingy, so you can just run the cronjob every minute/5
minutes/whatever and hardly think twice

Good insurance And I'll now take over the world