Want to avoid cron. Crons need to run in a separate web2py instance,
and there are some issues we've faced in keeping that alive and
running without memory issues.
-- Aditya
On Sep 10, 2:16 am, Michael Ellis <michael.f.el...@gmail.com> wrote:
> Others may have more experience with this, but it sounds like your
> example could be handled with a cron job that periodically checks for
> newly registered users. On GAE, you also have the option to use a
> task queue.
>
> On Sep 9, 7:05 am, Adi <aditya.sa...@gmail.com> wrote:
>
>
>
> > Hi,
>
> > I have this test case:
>
> > 1. User registers in app.
> > 2. App sends him greeting email ("Welcome to so-and-so app").
> > 3. App adds his email/name etc to mailing application (like Mailchimp)
> > for auto-subscribing to newsletter.
>
> > Now user expects steps 1 completion to take him to the next 'default/
> > index' page, and we don't want steps 2 and 3 to prevent completion of
> > step 1. Is there a way to make step 2 and 3 complete independently, in
> > a way that user's experience is not slowed down?
>
> > Think of it as being equivalent of asynchronous ajax request, which
> > doesn't wait for response before moving to the next piece of
> > javascript.
>
> > Any help on this? I know we should not create threads because web2py
> > handles that for us (read in some older post long long ago).
>
> > -- Adi
