Re: [WebDNA] Sending 100 mails an hour then pausing
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105996
interpreted = N
texte = --Boundary-01=_E5v5MI+ZpRyMdFo Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit > I actually wrote a WebDNA snippet that batch sent 100 > emails an hour awhile back. I took a more conservative approach by sending only one email per browser page reload. Since the refresh tag waits one second after the page has loaded (and considering the request and response time lag over the internet) the actual number of emails sent out were probably more like 30-50 per hour. But I wasn't in a hurry, I just wanted something I could observe while it was running. A simple click on the browser tab told me immediately how much of the db had been processed, how much was remaining, and which record had just been processed ... so I had live feedback in my browser the whole time. Nice! :) Each time a new request was sent my WebDNA code did a search for all records not previously marked as sent. By using "max=1" I was able to send only one email per request, and I marked that record "sent" so it could never be re-sent accidentally. Sincerely, Kenneth Grome --Boundary-01=_E5v5MI+ZpRyMdFo Content-Type: text/html; charset="iso-8859-6" Content-Transfer-Encoding: 7bit
> I actually wrote a WebDNA snippet that batch sent 100
> emails an hour awhile back.
I took a more conservative approach by sending only one email per browser page reload. Since the refresh tag waits one second after the page has loaded (and considering the request and response time lag over the internet) the actual number of emails sent out were probably more like 30-50 per hour.
But I wasn't in a hurry, I just wanted something I could observe while it was running. A simple click on the browser tab told me immediately how much of the db had been processed, how much was remaining, and which record had just been processed ... so I had live feedback in my browser the whole time. Nice! :)
Each time a new request was sent my WebDNA code did a search for all records not previously marked as sent. By using "max=1" I was able to send only one email per request, and I marked that record "sent" so it could never be re-sent accidentally.
Sincerely,
Kenneth Grome
--Boundary-01=_E5v5MI+ZpRyMdFo--
Associated Messages, from the most recent to the oldest:
--Boundary-01=_E5v5MI+ZpRyMdFo Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit > I actually wrote a WebDNA snippet that batch sent 100 > emails an hour awhile back. I took a more conservative approach by sending only one email per browser page reload. Since the refresh tag waits one second after the page has loaded (and considering the request and response time lag over the internet) the actual number of emails sent out were probably more like 30-50 per hour. But I wasn't in a hurry, I just wanted something I could observe while it was running. A simple click on the browser tab told me immediately how much of the db had been processed, how much was remaining, and which record had just been processed ... so I had live feedback in my browser the whole time. Nice! :) Each time a new request was sent my WebDNA code did a search for all records not previously marked as sent. By using "max=1" I was able to send only one email per request, and I marked that record "sent" so it could never be re-sent accidentally. Sincerely, Kenneth Grome --Boundary-01=_E5v5MI+ZpRyMdFo Content-Type: text/html; charset="iso-8859-6" Content-Transfer-Encoding: 7bit
> I actually wrote a WebDNA snippet that batch sent 100
> emails an hour awhile back.
I took a more conservative approach by sending only one email per browser page reload. Since the refresh tag waits one second after the page has loaded (and considering the request and response time lag over the internet) the actual number of emails sent out were probably more like 30-50 per hour.
But I wasn't in a hurry, I just wanted something I could observe while it was running. A simple click on the browser tab told me immediately how much of the db had been processed, how much was remaining, and which record had just been processed ... so I had live feedback in my browser the whole time. Nice! :)
Each time a new request was sent my WebDNA code did a search for all records not previously marked as sent. By using "max=1" I was able to send only one email per request, and I marked that record "sent" so it could never be re-sent accidentally.
Sincerely,
Kenneth Grome
--Boundary-01=_E5v5MI+ZpRyMdFo--
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
X etc.... (1999)
Merchant and WebCat 3.0 (1998)
emailer (1997)
more trouble with [showif] in [search] = busted [shownext] (2000)
Summary search -- speed (1997)
Targeted Redirect (1999)
[WriteFile] problems (1997)
WebCat 2.1 & WebStar 4.2 (2000)
Applescript, WebDNA, and PDF (1997)
Email within tmpl ? (1997)
SiteGaurd file Cache vs webcatalog cache (1997)
[ShowIf] and empty fields (1997)
More on the email templates (1997)
[WebDNA] How to use [function] (2012)
Multi-Row Tables from a search. (1997)
Protecting Files (2005)
Car Database (2002)
all records returned. (1997)
Status of variable hierarchy changes? (2000)
Sort Order on a page search (1997)