Re^4: Looping through database query to send emails is taking too long

I do have a note asking them to be patient, but I'd like a please wait screen to show while the sending is happening. Right now, even though I have the print line for the "please wait" before the actual loop, the browser doesn't show it until the messages are sent. It flashes briefly before the confirmation screen is shown. It defeats the purpose of it.

Comment on Re^4: Looping through database query to send emails is taking too long

Replies are listed 'Best First'.
Re^5: Looping through database query to send emails is taking too long by Anonymous Monk on Jul 21, 2015 at 07:03 UTC
...before the actual loop, the browser doesn't show it until the messages are sent. It flashes briefly before the confirmation screen is shown. It defeats the purpose of it. You need two processes One to tell the user , wait, wait, wait, its finished... using meta-refresh And one background process to query the database and send the emails Classic strategy is the following things :) Proc::Background, Highlander: one instance at a time (Oct 00), Watching long processes through CGI (Aug 02) , Throttling your web server (Oct 00) Modern strategy is use ajax or websockets, examples Mojolicious::Lite +and jQuery +AJAX + Mojo::Template, Re^3: real-time output from Mojolicious WebSockets? Still have to background the actual mailer ... but there might be an anyevent mail so you can avoid forking Either way separate the stuff	[reply]

Replies are listed 'Best First'.

Re^5: Looping through database query to send emails is taking too long
by Anonymous Monk on Jul 21, 2015 at 07:03 UTC

...before the actual loop, the browser doesn't show it until the messages are sent. It flashes briefly before the confirmation screen is shown. It defeats the purpose of it.

You need two processes

One to tell the user , wait, wait, wait, its finished... using meta-refresh

And one background process to query the database and send the emails

Classic strategy is the following things :) Proc::Background, Highlander: one instance at a time (Oct 00), Watching long processes through CGI (Aug 02) , Throttling your web server (Oct 00)

Modern strategy is use ajax or websockets, examples Mojolicious::Lite +and jQuery +AJAX + Mojo::Template, Re^3: real-time output from Mojolicious WebSockets?

Still have to background the actual mailer ... but there might be an anyevent mail so you can avoid forking

Either way separate the stuff

[reply]