Hi!
> * Insert the information into a queue (we typically use a database table).
> * Run a periodic poller on that database that generates the email (the
> period on the poller is determined by how long is an acceptable delay for
> your app, many times we use 5 -> 15 minutes).
That's the same ap
On Wed, 23 May 2007, Ash Berlin wrote:
mark wrote:
Exactly; sending the email in end() after the page has been sent off would
not delay the page loading...
Mark
Except that end is before the page has been sent back to the browser.
You would need some kind of hook in what ever engine you ar
Chisel Wright <[EMAIL PROTECTED]> wrote on 05/23/2007 04:32:31 AM:
> On Wed, May 23, 2007 at 07:41:21AM +0100, Mark Zealey wrote:
> > Why can you not do something like $c->stash->{emails_to_send} and then
just
> > fire them off in the end() action after the page has been returned to
the
> >
mark wrote:
Exactly; sending the email in end() after the page has been sent off would
not delay the page loading...
Mark
Except that end is before the page has been sent back to the browser.
You would need some kind of hook in what ever engine you are using to
support that. Not a bad idea
Exactly; sending the email in end() after the page has been sent off would
not delay the page loading...
Mark
___
List: Catalyst@lists.rawmode.org
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.
On Wed, May 23, 2007 at 07:41:21AM +0100, Mark Zealey wrote:
> Why can you not do something like $c->stash->{emails_to_send} and then just
> fire them off in the end() action after the page has been returned to the
> remote browser?
>
Because I don't want to spend any longer between *click* and
Why can you not do something like $c->stash->{emails_to_send} and then just
fire them off in the end() action after the page has been returned to the
remote browser?
M
On Tuesday 22 May 2007 10:31 pm, Chisel Wright wrote:
> On Tue, May 22, 2007 at 11:10:58AM -0700, Evaldas Imbrasas wrote:
> >
J,
I've looked at your module, but I'm afraid it would actually make
sending emails even more dependent on catalyst, and I want to be able
to use the same email framework from both catalyst and command-line
scripts.
In my setup, each email belongs to one emailclass. Metadata for each
emailclass,
On 5/22/07, Evaldas Imbrasas <[EMAIL PROTECTED]> wrote:
Hello list,
I'm looking for best practices for sending email from the catalyst app
that would also work with command-line scripts (cronjobs, one-time
scripts, etc.).
In my current setup, Email model takes care of storing metadata in the
d
On Tue, May 22, 2007 at 11:10:58AM -0700, Evaldas Imbrasas wrote:
> I'm looking for best practices for sending email from the catalyst app
> that would also work with command-line scripts (cronjobs, one-time
> scripts, etc.).
Personally I use a database table as a crude email queue. I should
proba
Hello list,
I'm looking for best practices for sending email from the catalyst app
that would also work with command-line scripts (cronjobs, one-time
scripts, etc.).
In my current setup, Email model takes care of storing metadata in the
database for each sent email, and Email controller has a pr
11 matches
Mail list logo
